CVE-2024-7073
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 · uneditedA server-side request forgery (SSRF) vulnerability exists in multiple WSO2 products due to improper input validation in SOAP admin services. This flaw allows unauthenticated attackers to manipulate server-side requests, enabling access to internal and external resources available through the network or filesystem. Exploitation of this vulnerability could lead to unauthorized access to sensitive data and systems, including resources within private networks, as long as they are reachable by the affected product.
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 confidenceWSO2 products contain an SSRF vulnerability due to improper input validation in SOAP admin services. Unauthenticated attackers can manipulate server-side requests to access internal networks, external resources, and potentially the filesystem if reachable by the affected server.
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= 5.2.0= 5.3.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0= 5.7.0= 5.8.0= 5.9.0= 5.10.0= 5.11.0= 6.0.0= 5.3.0= 5.5.0= 5.6.0= 5.7.0= 5.9.0= 5.10.0= 2.0.0= 1.3.0= 1.4.0= 1.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 WSO2 product and versionCheck the product version by inspecting the <PRODUCT_HOME>/repository/components/WSO2-Version.txt file, or log into the admin console and view the 'About' section. For WSO2 Identity Server, also check the <IS_HOME>/bin/wso2server.bat or wso2server.sh banner on startup.Affected if The installed product matches any version listed in the affected versions for WSO2 Identity Server (= 5.2.0 through 6.0.0), WSO2 Identity Server As Key Manager, WSO2 Open Banking Iam (= 2.0.0), or WSO2 Open Banking Km (= 1.3.0, 1.4.0, 1.5.0).
-
Verify SOAP admin service accessibilityConfirm whether the SOAP admin services are exposed by attempting to access the WSDL at https://<host>:9443/services/AdminService?wsdl (or port 9444 for some products). The vulnerability exists in the SOAP admin services endpoint.Affected if The SOAP admin services (AdminService) is reachable over the network without authentication restrictions.
-
Check outbound network configurationReview the <PRODUCT_HOME>/repository/conf/carbon.xml file for any network restrictions, and examine firewall rules or iptables settings that control outbound connections from the server.Affected if The WSO2 server has unrestricted outbound network access, allowing it to make arbitrary HTTP/HTTPS requests to internal or external resources.
A user is affected if they are running any of the listed WSO2 product versions with SOAP admin services exposed and the server has outbound network capability, enabling unauthenticated attackers to perform SSRF attacks.
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 dataImplement strict input validation on SOAP admin service parameters and restrict outbound network connections to prevent unauthorized resource access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7073 — 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-2024-7073 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