Is openssl-src affected by CVE-2021-3449?

crates.io openssl-src is affected in <111.15.0.

Is CVE-2021-3449 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 63.5%.

medium

CVE-2021-3449

Q: Is CVE-2021-3449 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 63.5%.

crates.io · openssl-src

Summary

openssl-src NULL pointer Dereference in signature_algorithms processing

Severity: medium
EPSS: 63.5% (p99)
Also known as: GHSA-83mx-573x-5rw9, BIT-node-2021-3449, BIT-node-min-2021-3449, RUSTSEC-2021-0055
Published: 2021-08-25

References

Related advisories

CVE-2022-4203 — critical · crates.io/openssl-src
CVE-2022-3602 — critical · crates.io/openssl-src
CVE-2021-3711 — critical · crates.io/openssl-src
CVE-2023-0215 — high · crates.io/openssl-src
CVE-2023-0216 — high · crates.io/openssl-src
CVE-2022-4450 — high · crates.io/openssl-src
CVE-2023-0217 — high · crates.io/openssl-src
CVE-2023-0401 — high · crates.io/openssl-src

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.