Skip to content
Fencer Intel
high —

GHSA-6hcf-g6gr-hhcr json

`openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereference

published 3y ago modified 3y ago also RUSTSEC-2023-0024

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

These functions would crash when the context argument was None with certain extension types.

Thanks to David Benjamin (Google) for reporting this issue.

Patch / fix

  • crates.io openssl 0.10.48

Is GHSA-6hcf-g6gr-hhcr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io openssl
>=0.9.7, <0.10.48
>=0.0.0-0, <0.10.48
0.10.48

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.