CVE-2022-32073

CRITICALNVD 9.89.8—Elevated

9.8

WolfSSH v1.4.7 was discovered to contain an integer overflow via the function wolfSSH_SFTP_RecvRMDIR.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 80.4%
KEV: Not listed

Published

July 13, 2022

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://github.com/wolfSSL/wolfssh/pull/360
af854a3a-2127-422b-91ae-364da2661108https://github.com/wolfSSL/wolfssh/pull/360

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-190Integer Overflow or Wraparound

Data Freshness Timeline

(refreshed 16× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

GitHub PoCmgregus/project_BIT_nmap_script
First seen Nov 29, 2022
Nmap .nse script to scan for CVE-2022-32073 in wolfssh
Open source ↗

Frequently asked(5)

What is CVE-2022-32073?

CVE-2022-32073 is a critical vulnerability published on July 13, 2022. WolfSSH v1.4.7 was discovered to contain an integer overflow via the function wolfSSHSFTPRecvRMDIR.

When was CVE-2022-32073 disclosed?

CVE-2022-32073 was first published in the National Vulnerability Database on July 13, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-32073 actively exploited?

CVE-2022-32073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 80.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-32073?

CVE-2022-32073 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2022-32073?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-32073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-32073

Explore →

Is Your Infrastructure Affected by CVE-2022-32073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2022-32073

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-32073?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)