GHSA-9qwg-crg9-m2vc json
`openssl` `SubjectAlternativeName` and `ExtendedKeyUsage::other` allow arbitrary file read
published 3y ago modified 3y ago also RUSTSEC-2023-0023
- 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
`SubjectAlternativeName` and `ExtendedKeyUsage` arguments were parsed using the OpenSSL function `X509V3_EXT_nconf`. This function parses all input using an OpenSSL mini-language which can perform arbitrary file reads.
Thanks to David Benjamin (Google) for reporting this issue.
Patch / fix
Is GHSA-9qwg-crg9-m2vc 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 FencerAffected 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
-
github.com
/sfackler/rust-openssl/pull/1854
web
-
github.com
/sfackler/rust-openssl
package
-
rustsec.org
/advisories/RUSTSEC-2023-0023.html
web, advisory
-
crates.io
/crates/openssl
package
Sources
- GitHub Advisory GHSA-9qwg-crg9-m2vc
- OSV RUSTSEC-2023-0023
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.