CVE-2020-24703
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 2.2.0, API Manager Analytics 2.2.0, API Microgateway 2.2.0, Data Analytics Server 3.2.0, Enterprise Integrator through 6.6.0, IS as Key Manager 5.5.0, Identity Server 5.5.0 and 5.8.0, Identity Server Analytics 5.5.0, and IoT Server 3.3.0 and 3.3.1.
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 · moderate confidenceThis vulnerability allows attackers to steal valid Carbon Management Console session cookies by tricking victims into submitting crafted 'Try It' requests. The session cookie gets exfiltrated to an attacker-controlled server, enabling full session hijacking and impersonation of authenticated users.
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= 2.2.0= 2.2.0= 2.2.0= 3.2.0<= 6.6.0= 5.5.0= 5.8.0= 5.5.0= 5.5.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 installed WSO2 product and versionLocate the product's version file or check the management console dashboard for the installed version number. Common locations: <product>/repository/components/VERSION or the About page in the Carbon Management Console.Affected if The installed version matches one of the affected versions: WSO2 API Manager = 2.2.0, API Manager Analytics = 2.2.0, API Microgateway = 2.2.0, Data Analytics Server = 3.2.0, Enterprise Integrator <= 6.6.0, Identity Server = 5.5.0 or = 5.8.0, Identity Server Analytics = 5.5.0, Identity Server As Key
-
Verify if Try It feature is enabledNavigate to the API Publisher or Developer Portal. Locate the Try It button on API endpoints. Check whether this feature is active and accessible to API consumers without authentication restrictions.Affected if The Try It feature is enabled and accessible to users, allowing them to send test requests directly from the API documentation interface.
-
Review API endpoint configurations for external domainsInspect the API definitions in the API Publisher. Look for any backend URLs or redirection parameters that point to external, unrecognized domains. Check API endpoint configurations for suspicious URL patterns or external hostnames.Affected if API endpoints are configured to redirect to or send requests toward untrusted or attacker-controlled external domains.
-
Inspect network logs for anomalous outbound connectionsReview server access logs and network traffic for any requests originating from the Try It feature that connect to external IP addresses or domains not belonging to your organization. Focus on requests containing session cookies or authentication tokens.Affected if Outbound requests from the Try It feature are being made to external IP addresses or domains, particularly those containing cookie data in the request path or headers.
-
Check for stored cross-site scripting or injection points in Try ItExamine the Try It feature's request parameters and API definitions for any unsanitized input fields that could allow injection of malicious URLs or scripts designed to exfiltrate cookies.Affected if The Try It feature accepts and processes unsanitized user input in request parameters, headers, or body content.
You are affected if your WSO2 product version matches the affected list AND the Try It feature is enabled, allowing crafted requests to exfiltrate session cookies to external domains.
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 dataApply vendor-provided security patches for all affected WSO2 products. Until patches are applied, consider disabling or restricting the Try It feature, implementing strict Content Security Policy headers, and monitoring for anomalous requests to external domains.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24703 — 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-24703 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