GHSA-v78c-4p63-2j6c — moment-timezone
Fix: moment/moment-timezone@7915ac5GHSA-v78c-4p63-2j6c is a security vulnerability in moment-timezone. A fix is available for moment-timezone — see the affected versions and patch details below.
Cleartext Transmission of Sensitive Information in moment-timezone
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
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.35npm install moment-timezone@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v78c-4p63-2j6c can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-v78c-4p63-2j6c across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.