Poly CCX devices: Missing Authentication for Critical Functionality
CVE-2024-3281 is a high-severity missing authentication for critical functionality vulnerability in Poly CCX devices from HP, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Poly CCX devices versions: See HP Security Bulletin reference for affected versions.. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Poly Ccx 350 to 8.1.3.1301 or a later version.
- Update Poly Ccx 400 to 8.1.3.1301 or a later version.
- Update Poly Ccx 500 to 8.1.3.1301 or a later version.
- Read the advisory on support.hp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| HP | Poly CCX devices | See HP Security Bulletin reference for affected versions. | Not stated |
| HP | Poly Ccx 350 | 8.0.2.3267 up to, but not including, 8.1.3.1301 | 8.1.3.1301 |
| HP | Poly Ccx 400 | 8.0.2.3267 up to, but not including, 8.1.3.1301 | 8.1.3.1301 |
| HP | Poly Ccx 500 | 8.0.2.3267 up to, but not including, 8.1.3.1301 | 8.1.3.1301 |
| HP | Poly Ccx 505 | 8.0.2.3267 up to, but not including, 8.1.1301 | 8.1.1301 |
| HP | Poly Ccx 600 | 8.0.2.3267 up to, but not including, 8.1.3.1301 | 8.1.3.1301 |
| HP | Poly Ccx 700 | 8.0.2.3267 up to, but not including, 8.1.3.1301 | 8.1.3.1301 |
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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H. Scored by CISA (ADP).
Official description
A vulnerability was discovered in the firmware builds after 8.0.2.3267 and prior to 8.1.3.1301 in CCX devices. A flaw in the firmware build process did not properly restrict access to a resource from an unauthorized actor.
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
Technical write-ups (may include proof of concept)
- syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2024-003.txtExploit, Third Party Advisory
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.