Summary
Cleartext Transmission of Sensitive Information in moment-timezone
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.
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)
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-V78C-4P63-2J6C? GHSA-V78C-4P63-2J6C is a medium-severity security vulnerability in moment-timezone (npm), affecting versions >= 0.1.0, < 0.5.35. It is fixed in 0.5.35.
- Which versions of moment-timezone are affected by GHSA-V78C-4P63-2J6C? moment-timezone (npm) versions >= 0.1.0, < 0.5.35 is affected.
- Is there a fix for GHSA-V78C-4P63-2J6C? Yes. GHSA-V78C-4P63-2J6C is fixed in 0.5.35. Upgrade to this version or later.
- Is GHSA-V78C-4P63-2J6C exploitable, and should I be worried? Whether GHSA-V78C-4P63-2J6C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-V78C-4P63-2J6C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-V78C-4P63-2J6C? Upgrade
moment-timezoneto 0.5.35 or later.