Versalink B400: Missing Authentication for Critical Functionality
CVE-2024-12511 is a high-severity missing authentication for critical functionality vulnerability in Versalink B400 from Xerox, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 37.82.53 as the first without the flaw, so updating Versalink B400 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Versalink B400 to 37.82.53 or a later version.
- Update Versalink B405 to 38.82.53 or a later version.
- Update Versalink C400 to 67.82.53 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Xerox | Versalink B400 | before 37.82.53 | 37.82.53 |
| Xerox | Versalink B405 | before 38.82.53 | 38.82.53 |
| Xerox | Versalink C400 | before 67.82.53 | 67.82.53 |
| Xerox | Versalink C405 | before 68.82.53 | 68.82.53 |
| Xerox | Versalink B600/B610 | before 32.82.53 | 32.82.53 |
| Xerox | Versalink B605/B615 | before 33.82.53 | 33.82.53 |
| Xerox | Versalink C500/C600 | before 61.82.53 | 61.82.53 |
| Xerox | Versalink C505/C605 | before 62.82.53 | 62.82.53 |
| Xerox | Versalink C7000 | before 56.75.53 | 56.75.53 |
| Xerox | Versalink C7020/C7025/C7030 | before 57.75.53 | 57.75.53 |
| Xerox | Versalink B7025/B7030/B7035 | before 58.75.53 | 58.75.53 |
| Xerox | Versalink B7125/B7130/B7135 | before 59.24.53 | 59.24.53 |
| Xerox | Versalink C7120/C7125/C7130 | before 69.24.53 | 69.24.53 |
| Xerox | Versalink C8000/C9000 | before 70.75.53 | 70.75.53 |
| Xerox | Versalink C8000W | before 72.75.53 | 72.75.53 |
| Xerox | Phaser 6510 | before 64.75.53 | 64.75.53 |
| Xerox | WorkCentre 6515 | before 65.75.53 | 65.75.53 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L. Scored by CNA.
Official description
With address book access, SMB/FTP settings could be modified, redirecting scans and possibly capturing credentials. This requires enabled scan functions and printer access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Missing Authentication for Critical Functionality vulnerabilities
- 8.4 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.6 High severity
Spotted an error? Tell us.