How severe is GHSA-3fg9-hcq5-vxrc?

No CVSS score has been assigned to GHSA-3fg9-hcq5-vxrc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3fg9-hcq5-vxrc?

GHSA-3fg9-hcq5-vxrc affects the following packages: iana-time-zone (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-3fg9-hcq5-vxrc?

Update iana-time-zone to 0.1.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3fg9-hcq5-vxrc is resolved across your whole dependency graph.

How do I detect GHSA-3fg9-hcq5-vxrc in my crates.io dependencies?

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

How do I mitigate GHSA-3fg9-hcq5-vxrc 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-3fg9-hcq5-vxrc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3fg9-hcq5-vxrc can be triaged on real exposure rather than presence alone.

Is GHSA-3fg9-hcq5-vxrc actively exploited in the wild?

No public exploit code has been indexed for GHSA-3fg9-hcq5-vxrc 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-3fg9-hcq5-vxrc published, and has it been updated?

GHSA-3fg9-hcq5-vxrc was published on August 30, 2022 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

GHSA-3fg9-hcq5-vxrc — iana-time-zone

Fix: strawlab/iana-time-zone#54

GHSA-3fg9-hcq5-vxrc is a security vulnerability in iana-time-zone. A fix is available for iana-time-zone — see the affected versions and patch details below.

iana-time-zone vulnerable to use after free in MacOS / iOS implementation

Also known asRUSTSEC-2022-0049

Published

Aug 30, 2022

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

🦀iana-time-zone

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

In iana-time-zone v0.1.43 a use-after-free bug in the MacOS / iOS implementation was introduced.

The copied system time zone was released before its name was copied. If the system time zone was changed between the call of CFRelease and str::to_owned(), random memory would be copied.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`iana-time-zone`	≥ 0.1.43&&< 0.1.45	0.1.45`cargo update -p iana-time-zone --precise 0.1.45`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for iana-time-zone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update iana-time-zone to 0.1.45 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3fg9-hcq5-vxrc 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3fg9-hcq5-vxrc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3fg9-hcq5-vxrc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In iana-time-zone v0.1.43 a use-after-free bug in the MacOS / iOS implementation was introduced. The copied system time zone was released before its name was copied. If the system time zone was changed between the call of `CFRelease` and `str::to_owned()`, random memory would be copied.

O3 Security · Impact-Aware SCA

Is GHSA-3fg9-hcq5-vxrc in your dependencies?

O3 Security finds GHSA-3fg9-hcq5-vxrc across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works