Extreme XDS: Insertion of Sensitive Information Into Sent Data
CVE-2024-7872 is a high-severity insertion of sensitive information into sent data vulnerability in Extreme XDS from ExtremePacs, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 3933 as the first without the flaw, so updating Extreme XDS to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% 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 Extreme XDS to 3933 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ExtremePACS | Extreme XDS | before 3933 | 3933 |
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
- 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:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L. Scored by CNA (usom.gov.tr).
Official description
Insertion of Sensitive Information Into Sent Data vulnerability in ExtremePACS Extreme XDS allows Retrieve Embedded Sensitive Data. This issue affects Extreme XDS: before 3933.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
How developers prevent this class of flaw
- Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
- Setup default error messages so that unexpected errors do not disclose sensitive information.
More Insertion of Sensitive Information Into Sent Data vulnerabilities (CWE-201)
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
Other vulnerabilities in Extreme XDS
- 8.8 High severity
- 7.2 High severity
Recent Insertion of Sensitive Information Into Sent Data vulnerabilities
- 8.3 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.