wolfSSL 4.6.x through 4.7.x before 4.8.0 does not produce a failure outcome when the serial number in an OCSP request differs from the serial number in the OCSP response.
Loading...
Loading...
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 33% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
wolfSSL 4.6.x through 4.7.x before 4.8.0 does not produce a failure outcome when the serial number in an OCSP request differs from the serial number in the OCSP response.
July 21, 2021
November 21, 2024
Patch available: wolfSSL/wolfssl v4.8.0-stable
https://github.com/wolfSSL/wolfssl/releases/tag/v4.8.0-stableFix merged in wolfSSL/wolfssl PR #3990 on 2021-04-28 — awaiting tagged release
https://github.com/wolfSSL/wolfssl/pull/3990Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-37155
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.