Immutable.js provides many Persistent Immutable data structures. Prior to 4.3.9 and 5.1.8, Immutable.Map and Immutable.Set keep keys that share the same 32-bit hash in a HashCollisionNode collision bucket that is scanned linearly, allowing an attacker who controls keys inserted into a Map, such as through Immutable.Map(obj), Immutable.fromJS(obj), state.merge(userObject), or mergeDeep, to craft many colliding keys and degrade insertion and lookup to consume disproportionate CPU. This issue is fixed in versions 4.3.9 and 5.1.8.
| Vendor | Product | Versions |
|---|---|---|
| immutable-js | immutable-js | npm/immutable: < 4.3.9, npm/immutable: >= 5.0.0-beta.1, < 5.1.8 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| ibm | tivoli netcool/omnibus | cert_advisory | 90% |
| npm | immutable | GHSA | 85% |
Updated affected versions to include < 4.3.8 and < 5.1.7, changed severity to HIGH, and noted that no exploit exists.
Initial creation
