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.
Weakness
An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Immutable | Immutable-js | * | 4.3.9 (excluding) |
| Immutable | Immutable-js | 5.0.0 (including) | 5.1.8 (excluding) |
| Node-immutable | Ubuntu | questing | * |
References
- https://github.com/immutable-js/immutable-js/commit/3dd7e5655012597a41873e328bf9142a8901527b
- https://github.com/immutable-js/immutable-js/commit/e51d49fc612ded5ec4dfb94ff294d22074269b0f
- https://github.com/immutable-js/immutable-js/releases/tag/v4.3.9
- https://github.com/immutable-js/immutable-js/releases/tag/v5.1.8
- https://github.com/immutable-js/immutable-js/security/advisories/GHSA-xvcm-6775-5m9r
- https://github.com/immutable-js/immutable-js/security/advisories/GHSA-xvcm-6775-5m9r