cumulative-distribution-function
Affected
- introduced
0, fixed2.0.0(semver)
Fixed versions
2.0.0
Fix
- Fixed version
2.0.0npm install [email protected]
Advisory
Also known as: CVE-2021-29486
cumulative-distribution-function Infinite Loop vulnerability
Impact
A flaw enabling an infinite-loop was discovered in the code for evaluating the cumulative-distribution-function
of input data. Although the documentation explains that numeric data is required, some users may confuse an array
of strings like ["1","2","3","4","5"] for numeric data [1,2,3,4,5] when it is in fact string data. An infinite loop is possible when the
cumulative-distribution-function is evaluated for a given point when the input data is string data rather than type number.
This vulnerability enables an infinite-cpu-loop denial-of-service-attack on any app using npm:cumulative-distribution-function v1.0.3 or earlier if the attacker can supply malformed data to the library. The vulnerability could also manifest if a data source to
be analyzed changes data type from Arrays of number (proper) to Arrays of string (invalid, but undetected by earlier version of the library).
Patches
Users should upgrade to at least v2.0.0, or the latest version.
Tests for several types of invalid data have been created, and version 2.0.0 has been tested to reject this invalid data by
throwing a TypeError() instead of processing it. Developers using this library may wish to adjust their app's code slightly to better tolerate or handle this TypeError. Apps performing proper numeric data validation before sending data to this library should be mostly unaffected by this patch.
Workarounds
The vulnerability can be mitigated in older versions by ensuring that only finite numeric data of type Array[number] or number is passed to cumulative-distribution-function and its f(x) function, respectively.
For more information
If you have any questions or comments about this advisory:
High Basis: The source's own band: HIGH
0, fixed 2.0.0 (semver)2.0.0
2.0.0npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0