WSO2 API Manager: Improper Restriction of XML External Entity Reference
CVE-2024-2374 is a critical-severity improper restriction of XML external entity reference vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 3.1.0.278, 3.2.0.368, 4.0.0.280 as the first without the flaw, so updating WSO2 API Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update WSO2 API Manager to 3.1.0.278 or 3.2.0.368 or 4.0.0.280 or 4.1.0.206, whichever matches your release line, or a later version.
- Update WSO2 Identity Server to 5.10.0.300 or 5.11.0.329 or 6.0.0.179 or 6.1.0.136, whichever matches your release line, or a later version.
- Update WSO2 Open Banking AM to 2.0.0.328 or a later version.
- Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WSO2 | WSO2 API Manager | 3.1.0 up to, but not including, 3.1.0.278; 3.2.0 up to, but not including, 3.2.0.368; 4.0.0 up to, but not including, 4.0.0.280; 4.1.0 up to, but not including, 4.1.0.206; 4.2.0 up to, but not including, 4.2.0.144; 4.3.0 up to, but not including, 4.3.0.57 | 3.1.0.278, 3.2.0.368, 4.0.0.280, 4.1.0.206, 4.2.0.144, 4.3.0.57 |
| WSO2 | WSO2 Identity Server | 5.10.0 up to, but not including, 5.10.0.300; 5.11.0 up to, but not including, 5.11.0.329; 6.0.0 up to, but not including, 6.0.0.179; 6.1.0 up to, but not including, 6.1.0.136 | 5.10.0.300, 5.11.0.329, 6.0.0.179, 6.1.0.136 |
| WSO2 | WSO2 Open Banking AM | 2.0.0 up to, but not including, 2.0.0.328 | 2.0.0.328 |
| WSO2 | WSO2 Open Banking IAM | 2.0.0 up to, but not including, 2.0.0.348 | 2.0.0.348 |
| WSO2 | WSO2 Identity Server as Key Manager | 5.10.0 up to, but not including, 5.10.0.296 | 5.10.0.296 |
| WSO2 | API Manager | 3.1.0 up to, but not including, 3.1.0.278; 3.2.0 up to, but not including, 3.2.0.368; 4.0.0 up to, but not including, 4.0.0.280; 4.1.0 up to, but not including, 4.1.0.206; 4.2.0 up to, but not including, 4.2.0.144; 4.3.0 up to, but not including, 4.3.0.57 | 3.1.0.278, 3.2.0.368, 4.0.0.280, 4.1.0.206, 4.2.0.144, 4.3.0.57 |
| WSO2 | Identity Server | 5.10.0 up to, but not including, 5.10.0.300; 5.11.0 up to, but not including, 5.11.0.329; 6.0.0 up to, but not including, 6.0.0.179; 6.1.0 up to, but not including, 6.1.0.136 | 5.10.0.300, 5.11.0.329, 6.0.0.179, 6.1.0.136 |
| WSO2 | Identity Server As Key Manager | 5.10.0 up to, but not including, 5.10.0.296 | 5.10.0.296 |
| WSO2 | Open Banking Am | 2.0.0 up to, but not including, 2.0.0.328 | 2.0.0.328 |
| WSO2 | Open Banking Iam | 2.0.0 up to, but not including, 2.0.0.348 | 2.0.0.348 |
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
- 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
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA |
| CVSS 3.1 | 9.1 | Critical | NVD |
Official description
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the resolution of external entities. This omission allows malicious actors to craft XML payloads that exploit the parser's behavior, leading to the inclusion of external resources. By leveraging this vulnerability, an attacker can read confidential files from the file system and access limited HTTP resources reachable by the product. Additionally, the vulnerability can be exploited to perform denial of service attacks by exhausting server resources through recursive entity expansion or fetching large external resources.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of XML External Entity Reference
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
How developers prevent this class of flaw
- Many XML parsers and validators can be configured to disable external entity expansion.
More Improper Restriction of XML External Entity Reference vulnerabilities (CWE-611)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in WSO2 API Manager
- 9.8 Critical severity
- 8.7 High severity
- 9.4 Critical severity
- 8.3 High severity
- 9.1 Critical severity
- 8.4 High severity
Recent Improper Restriction of XML External Entity Reference vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 7.6 High severity
- 8.6 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.