GHSA-v78c-4p63-2j6c
Cleartext Transmission of Sensitive Information in moment-timezone
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
moment-timezonenpmDescription
Impact
- if Alice uses
grunt data(orgrunt release) to prepare a custom-build, moment-timezone with the latest tzdata from IANA's website - and Mallory intercepts the request to IANA's unencrypted ftp server, Mallory can serve data which might exploit further stages of the moment-timezone tzdata pipeline, or potentially produce a tainted version of moment-timezone (practicality of such attacks is not proved)
Patches
Problem has been patched in version 0.5.35, patch should be applicable with minor modifications to all affected versions. The patch includes changing the FTP endpoint with an HTTPS endpoint.
Workarounds
Specify the exact version of tzdata (like 2014d, full command being grunt data:2014d, then run the rest of the release tasks by hand), or just apply the patch before issuing the grunt command.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | moment-timezone | ≥ 0.1.0&&< 0.5.35 | 0.5.35 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moment-timezone. 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 moment-timezone to 0.5.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v78c-4p63-2j6c 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-v78c-4p63-2j6c 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-v78c-4p63-2j6c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v78c-4p63-2j6c in your dependencies?
O3 detects GHSA-v78c-4p63-2j6c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.