How severe is GHSA-c8v3-jhv9-4ppc?

No CVSS score has been assigned to GHSA-c8v3-jhv9-4ppc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c8v3-jhv9-4ppc?

GHSA-c8v3-jhv9-4ppc affects the following packages: rust-i18n-support (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-c8v3-jhv9-4ppc?

Update rust-i18n-support to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8v3-jhv9-4ppc is resolved across your whole dependency graph.

How do I detect GHSA-c8v3-jhv9-4ppc in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rust-i18n-support. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-c8v3-jhv9-4ppc 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.

How does O3 Security protect against GHSA-c8v3-jhv9-4ppc?

O3 pinpoints whether GHSA-c8v3-jhv9-4ppc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-c8v3-jhv9-4ppc actively exploited in the wild?

No public exploit code has been indexed for GHSA-c8v3-jhv9-4ppc 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-c8v3-jhv9-4ppc published, and has it been updated?

GHSA-c8v3-jhv9-4ppc was published on January 23, 2024 and was last updated on February 10, 2024. 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

GHSA-c8v3-jhv9-4ppc

Use-after-free when setting the locale

Also known asRUSTSEC-2024-0007

Published

Jan 23, 2024

Updated

Feb 10, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀rust-i18n-support

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

Version 3.0.0 introduced an AtomicStr type, that is used to store the current locale. It stores the locale as a raw pointer to an Arc<String>. The locale can be read with AtomicStr::as_str(). AtomicStr::as_str() does not increment the usage counter of the Arc.

If the locale is changed in one thread, another thread can have a stale -- possibly already freed -- reference to the stored string.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rust-i18n-support`	≥ 3.0.0&&< 3.0.1	3.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rust-i18n-support. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update rust-i18n-support to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8v3-jhv9-4ppc 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.
How O3 protects you
O3 pinpoints whether GHSA-c8v3-jhv9-4ppc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c8v3-jhv9-4ppc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 3.0.0 introduced an `AtomicStr` type, that is used to store the current locale. It stores the locale as a raw pointer to an `Arc<String>`. The locale can be read with `AtomicStr::as_str()`. `AtomicStr::as_str()` does not increment the usage counter of the `Arc`. If the locale is changed in one thread, another thread can have a stale -- possibly already freed -- reference to the stored string.

O3 Security · Impact-Aware SCA

Is GHSA-c8v3-jhv9-4ppc in your dependencies?

O3 detects GHSA-c8v3-jhv9-4ppc across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works