CVE-2022-29464
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 · uneditedCertain WSO2 products allow unrestricted file upload with resultant remote code execution. The attacker must use a /fileupload endpoint with a Content-Disposition directory traversal sequence to reach a directory under the web root, such as a ../../../../repository/deployment/server/webapps directory. This affects WSO2 API Manager 2.2.0 up to 4.0.0, WSO2 Identity Server 5.2.0 up to 5.11.0, WSO2 Identity Server Analytics 5.4.0, 5.4.1, 5.5.0 and 5.6.0, WSO2 Identity Server as Key Manager 5.3.0 up to 5.11.0, WSO2 Enterprise Integrator 6.2.0 up to 6.6.0, WSO2 Open Banking AM 1.4.0 up to 2.0.0 and WSO2 Open Banking KM 1.4.0, up to 2.0.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 confidenceWSO2 products contain an unrestricted file upload vulnerability in /fileupload endpoints. Attackers exploit this by including directory traversal sequences (../../../) in the Content-Disposition header to write malicious files (e.g., JSP webshells) to web-accessible directories under the web root, specifically the repository/deployment/server/webapps folder, achieving remote code execution.
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, <= 4.0.0>= 6.2.0, <= 6.6.0>= 5.2.0, <= 5.11.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0>= 5.3.0, <= 5.10.0>= 1.3.0, <= 2.0.0= 2.0.0>= 1.3.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 WSO2 product and versionLocate the version file in your WSO2 installation (typically in the product's root directory or repository/conf/etc), or query the admin console/metadata endpoint for the running versionAffected if The installed version falls within any of these ranges: API Manager 2.2.0-4.0.0, Enterprise Integrator 6.2.0-6.6.0, Identity Server 5.2.0-5.11.0, Identity Server Analytics 5.4.0/5.4.1/5.5.0/5.6.0, Identity Server as Key Manager 5.3.0-5.10.0, Open Banking AM 1.3.0-2.0.0, Open Banking IAM 2.0.0, or Op
-
Verify /fileupload endpoint exposureAttempt a local curl request to the fileupload endpoint (e.g., POST to /fileupload/toolsAny) or check your reverse proxy/firewall rules to determine if these endpoints are accessible from untrusted networksAffected if The /fileupload endpoints are reachable from outside trusted networks without authentication controls
-
Inspect webapps directory for unauthorized filesExamine the webapps directory (repository/deployment/server/webapps or similar deployment path) for unexpected .jsp files with suspicious names, especially those not deployed through standard WSO2 toolingAffected if Unexpected .jsp files exist in the webapps directory that were not intentionally deployed by administrators
-
Review access logs for exploitation patternsSearch HTTP access logs (found in repository/logs/http_access_*.log) for requests to /fileupload endpoints containing directory traversal sequences (../) in Content-Disposition headers or unusual file extensionsAffected if Logs contain POST requests to /fileupload with ../../ sequences in headers or uploaded .jsp files to non-standard paths
You are affected if you run any WSO2 product version within the listed ranges AND your /fileupload endpoints are network-accessible, or if you find unexpected JSP files in your webapps directory or exploitation attempts in your logs.
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.
dbcve · scopedApply vendor-provided security patches or upgrade to fixed versions; if patching is immediately unavailable, block or restrict access to /fileupload endpoints via WAF rules or network segmentation, and ensure uploaded files in web-accessible directories cannot be executed.
Upgrade to the latest stable release of your WSO2 product (e.g., API Manager 4.0.1+, EI 6.6.1+, IS 5.11.1+, IS Analytics 5.7.0+, IS as KM 5.11.1+, Open Banking AM/KM 2.0.1+)
- 1. Identify the specific WSO2 product and current version from the affected list (API Manager, Enterprise Integrator, Identity Server, etc.)
- 2. Determine the appropriate fixed version for your product: API Manager upgrade to 4.0.1 or later; Enterprise Integrator upgrade to 6.6.1 or later; Identity Server upgrade to 5.11.1 or later; Identity Server Analytics upgrade to 5.7.0 or later; Identity Server as Key Manager upgrade to 5.11.1 or later; Open Banking AM upgrade to 2.0.1 or later; Open Banking KM upgrade to 2.0.1 or later
- 3. Review WSO2 security advisories at security.docs.wso2.com for any specific patch requirements for your exact version
- 4. Create a backup of the current installation including repository/deployment directory
- 5. Test the upgrade in a staging environment before production deployment
- 6. Upgrade the production environment to the fixed version
- 7. Verify the /fileupload endpoints no longer accept directory traversal sequences (../) in Content-Disposition headers
- 8. After upgrade, confirm web applications deploy correctly in repository/deployment/server/webapps
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29464 — 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-2022-29464 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