CVE-2020-24705
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 · uneditedAn issue was discovered in certain WSO2 products. A valid Carbon Management Console session cookie may be sent to an attacker-controlled server if the victim submits a crafted Try It request, aka Session Hijacking. This affects API Manager through 3.1.0, API Manager Analytics 2.5.0, IS as Key Manager through 5.10.0, Identity Server through 5.10.0, Identity Server Analytics through 5.6.0, and IoT Server 3.1.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 confidenceThis is a session hijacking vulnerability in WSO2 products where the Carbon Management Console session cookie can be exfiltrated to an attacker-controlled server when a victim submits a crafted 'Try It' request (API testing feature). The attacker crafts a malicious request that causes the victim's valid session cookie to be sent to a server under the attacker's control, enabling full session takeover.
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.1.0= 2.5.0<= 5.10.0<= 5.6.0<= 5.10.0= 3.1.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 the installed WSO2 product and versionCheck the startup banner or logs for the product name and version number. Alternatively, access the Carbon Management Console (typically at /carbon or /console) and look for the version information in the footer or about page.Affected if The product is one of: WSO2 API Manager <=3.1.0, WSO2 API Manager Analytics =2.5.0, WSO2 Identity Server <=5.10.0, WSO2 Identity Server Analytics <=5.6.0, WSO2 Identity Server as Key Manager <=5.10.0, or WSO2 IOT Server =3.1.0
-
Confirm the Try It feature is enabledLocate the configuration file that governs the API testing feature. In WSO2 API Manager, this is typically the api-manager.xml file in the repository/conf directory. Look for settings related to 'Try It' or API testing that enable this functionality.Affected if The Try It feature or API testing functionality is turned on in the product configuration
-
Check for the Carbon Management Console accessibilityVerify that the Carbon Management Console (usually accessed via /carbon endpoint) is accessible. This console handles session management and is the target of cookie exfiltration.Affected if The Carbon Management Console is accessible to users who can make API requests through the Try It feature
-
Review outbound network connections from the applicationExamine network logs or proxy configurations to determine if the application is permitted to make outbound HTTP/HTTPS connections to arbitrary servers. This is required for the cookie exfiltration to succeed.Affected if The application can initiate outbound connections to attacker-controlled servers from the server hosting the WSO2 product
Your environment is affected if you run any of the listed WSO2 product versions with the Try It feature enabled and the Carbon Management Console accessible, combined with the ability for the server to make outbound network connections.
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 dataUpgrade affected WSO2 products to the latest patched versions as specified in WSO2 security advisories. If immediate patching is not feasible, consider disabling or restricting the Try It feature and implementing additional network-level controls to prevent outbound connections from the application to untrusted servers.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24705 — 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-24705 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