`openssl` `X509NameBuilder::build` returned object is not thread safe
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
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.
Why it matters now
Fix Fixed openssl (crates.io): 0.10.48
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openssl (crates.io) | 0.9.7 to before 0.10.48 | 0.10.48 | Patch available | GHSA-3gxf-9r58-2ghg |
- openssl (crates.io) Vendor— Affected 0.9.7 to before 0.10.48 Fixed in 0.10.48 Patch available GHSA-3gxf-9r58-2ghg
Remediation
- Fix · GHSA-3gxf-9r58-2ghg openssl (crates.io) Fixed in 0.10.48 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-3gxf-9r58-2ghg
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences