Email me

Rust advisories / openssl-src

Vulnerability HighRUSTSEC-2023-0006 · openssl-src

RUSTSEC-2023-0006: X.400 address type confusion in X.509 `GeneralName`

Short answerA security vulnerability in the openssl-src crate: X.400 address type confusion in X.509 `GeneralName`. GitHub rates it High. Fixed in 111.25.0, 300.0.12: update to a fixed version.

Crateopenssl-src
TypeVulnerability (denial-of-service, memory-exposure)
Affected versionsBefore 111.25.0; from 300.0.0 before 300.0.12.
Fixed in111.25.0, 300.0.12
SeverityHigh (GitHub rating)
Published2023-02-07
Last changed2026-07-07
Also known asCVE-2023-0286, GHSA-x4qr-2fvf-3mr5, PYSEC-2026-800

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

There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.

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