Email me

Rust advisories / openssl-src

Vulnerability CriticalRUSTSEC-2023-0008 · openssl-src

RUSTSEC-2023-0008: X.509 Name Constraints Read Buffer Overflow

Short answerA security vulnerability in the openssl-src crate: X.509 Name Constraints Read Buffer Overflow. GitHub rates it Critical. Fixed in 300.0.12: update to a fixed version.

Crateopenssl-src
TypeVulnerability (denial-of-service, memory-exposure)
Affected versionsFrom 300.0.0 before 300.0.12.
Fixed in300.0.12
SeverityCritical (GitHub rating)
Published2023-02-07
Last changed2023-11-08
Also known asCVE-2022-4203, GHSA-w67w-mw4j-8qrv

What to do

  1. See which version you have: cargo tree -i openssl-src (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p openssl-src. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example openssl-src = "300.0.12") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for openssl-src

Full security history of openssl-src

Up next

Same crateopenssl-src: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ