Threadlinqs IntelligenceStart free

VulnerabilityCVE-2022-29464Published 2022-04-18

CVE-2022-29464

criticalCISA KEVRansomwarePublic exploit11 PoC reposNuclei template

As of 2025-10-21, CVE-2022-29464 is a CRITICAL-severity vulnerability, CVSS v3.1 9.8, EPSS 99.9% (99.9th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-25), with a US federal remediation deadline of 2022-05-16, and CISA links it to known ransomware campaigns. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2022-29464, most recently “Evooo1Bot: Multi-Functional Mirai-Based Linux Botnet Exploiting 18 Known CVEs in Internet-Facing Devices”.

CVSS v3.1
9.8/10Critical
EPSS
99.9%Higher than 99.9% of scored CVEs
CISA KEV
ListedAdded · due 2022-05-16
Tracked threats
1Campaigns referencing it
Priority
10/10Threadlinqs triage score
Published
Updated 2025-10-21
CVSS v3.1 9.8 (CRITICAL) · EPSS 99.9% (higher than 99.9% of all scored CVEs) · Priority 10/10 · Published 2022-04-18

Last updated:

What is CVE-2022-29464?

Certain 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.

The record classifies CVE-2022-29464 under weakness class CWE-22. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. The identifier was first published 1636 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N
EPSS (FIRST)
99.9% probability of exploitation in the next 30 days, higher than 99.9% of all scored CVEs
CISA KEV
Listed since 2022-04-25, federal remediation deadline 2022-05-16 — used in known ransomware campaigns
Threadlinqs priority
10/10 — CISA lists it as used in ransomware, which Threadlinqs scores at the maximum
Published
2022-04-18, last modified 2025-10-21

Is CVE-2022-29464 being exploited?

CISA added CVE-2022-29464 to the Known Exploited Vulnerabilities catalog on 2022-04-25, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-05-16 under BOD 22-01. CISA flags the vulnerability as one used in known ransomware campaigns. Weaponised exploit code for CVE-2022-29464 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2022/CVE-2022-29464.yaml). It currently carries a trending score of 50 in the Threadlinqs vulnerability feed.

Affected products and versions

No affected-product or package list has been recorded for CVE-2022-29464 in the tracked sources. The vendor advisory and the references below are the authoritative statement of what is affected.

How to fix CVE-2022-29464

Because CVE-2022-29464 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-05-16. No vendor patch reference has been recorded for CVE-2022-29464 in the tracked sources. Follow the references below for a fix, and treat any affected deployment as exposed until the vendor states otherwise.

Threat activity tracking CVE-2022-29464

1 tracked threat in the Threadlinqs corpus references CVE-2022-29464, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on .

Mailing list and disclosure

Other references