Is tokio-boring affected by CVE-2023-6180?

crates.io tokio-boring is affected in >=4.0.0 <4.1.0.

Is CVE-2023-6180 being exploited?

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

medium

CVE-2023-6180

Q: Is CVE-2023-6180 being exploited?

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

crates.io · tokio-boring

Summary

tokio-boring vulnerable to resource exhaustion via memory leak

Severity: medium
EPSS: 0.6% (p45)
Also known as: GHSA-pjrj-h4fg-6gm4
Published: 2023-12-05

References

https://github.com/cloudflare/boring/security/advisories/GHSA-pjrj-h4fg-6gm4
https://nvd.nist.gov/vuln/detail/CVE-2023-6180
https://github.com/cloudflare/boring/commit/a32783374f2682e6949fdb713910b1b9f103d3ed

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.