CVE-2020-24591
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Management Console in certain WSO2 products allows XXE attacks during EventReceiver updates. This affects API Manager through 3.0.0, API Manager Analytics 2.2.0 and 2.5.0, API Microgateway 2.2.0, Enterprise Integrator 6.2.0 and 6.3.0, and Identity Server Analytics through 5.6.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WSO2 Management Console contains an XML External Entity (XXE) vulnerability in the EventReceiver update functionality. The XML parser used during EventReceiver configuration updates processes external entity references without proper sanitization, allowing authenticated attackers to inject malicious XML that can access local files or perform server-side request forgery.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.0.0= 2.2.0= 2.5.0= 2.2.0= 6.2.0= 6.3.0<= 5.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed WSO2 product and versionLocate the version file in the WSO2 installation directory, typically in the root folder or check the management console about page for the exact version numberAffected if The installed version matches: API Manager <= 3.0.0, API Manager Analytics 2.2.0 or 2.5.0, API Microgateway 2.2.0, Enterprise Integrator 6.2.0 or 6.3.0, Identity Server Analytics <= 5.6.0
-
Verify Management Console access is enabledConfirm that the WSO2 Management Console is accessible, typically on port 9443 or 9444 with the /carbon endpointAffected if The Management Console is reachable and accepts authentication
-
Confirm EventReceiver functionality is presentLog into the Management Console and navigate to the Analytics or Eventing sections to verify the EventReceiver update feature existsAffected if The EventReceiver configuration update functionality is available in the management interface
-
Check XML parser configuration for external entity processingExamine the XML parser configuration files (typically axis2.xml or similar XML parser configuration) to determine if external entity processing is disabledAffected if The XML parser has NOT disabled external entity (XXE) processing - the setting for disallowing external entities is not configured or is set to allow
The environment is affected if the installed WSO2 product version is within the affected ranges AND the Management Console with EventReceiver functionality is accessible AND the XML parser configuration allows external entity processing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to patched versions of the affected WSO2 products (API Manager 3.0.1+, API Manager Analytics 2.2.1+/2.5.1+, API Microgateway 2.2.1+, Enterprise Integrator 6.2.1+/6.3.1+, Identity Server Analytics 5.6.1+). As a compensating control, disable external entity processing in the XML parser configuration for the Management Console.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24591 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24591 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data