How severe is GHSA-6hcf-g6gr-hhcr?

No CVSS score has been assigned to GHSA-6hcf-g6gr-hhcr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6hcf-g6gr-hhcr?

GHSA-6hcf-g6gr-hhcr affects the following packages: openssl (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6hcf-g6gr-hhcr?

Update openssl to 0.10.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hcf-g6gr-hhcr is resolved across your whole dependency graph.

How do I detect GHSA-6hcf-g6gr-hhcr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6hcf-g6gr-hhcr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6hcf-g6gr-hhcr actively exploited in the wild?

No public exploit code has been indexed for GHSA-6hcf-g6gr-hhcr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6hcf-g6gr-hhcr published, and has it been updated?

GHSA-6hcf-g6gr-hhcr was published on March 24, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

`openssl` `X509Extension::new` and `X509Extension::new_nid` null pointer dereferenceGHSA-6hcf-g6gr-hhcr

Fix: sfackler/rust-openssl#1854

GHSA-6hcf-g6gr-hhcr is a security vulnerability in openssl. A fix is available for openssl — see the affected versions and patch details below.

Also known asRUSTSEC-2023-0024

Published

Mar 24, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀openssl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl`	≥ 0.9.7&&< 0.10.48	0.10.48`cargo update -p openssl --precise 0.10.48`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl to 0.10.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hcf-g6gr-hhcr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

These functions would crash when the context argument was None with certain extension types. Thanks to David Benjamin (Google) for reporting this issue.

O3 Security · Impact-Aware SCA

Is GHSA-6hcf-g6gr-hhcr in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works