Skip to content
Fencer Intel
medium —

GHSA-3gxf-9r58-2ghg json

`openssl` `X509NameBuilder::build` returned object is not thread safe

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

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

OpenSSL has a `modified` bit that it can set on on `X509_NAME` objects. If this bit is set then the object is not thread-safe even when it appears the code is not modifying the value.

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

Patch / fix

  • crates.io openssl 0.10.48

Is GHSA-3gxf-9r58-2ghg 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

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.