Packages / msgpackr / Security
msgpackr's conversion of property names to strings can trigger infinite recursion
Affected releases · msgpackr
- 1.x1.0.0 – 1.10.0Fixed in 1.10.1
- 0.6.x and older0.1.0 – 0.6.0No fix, no longer updated
On 1.x, the newest line:
npm install msgpackr@1.10.1Every release on a timeline
Not affected
2.0.0 – 2.1.4
12 releases, latest
Affected
1.0.0 – 1.10.0
71 releases
Fixed
1.10.1 – 1.12.1
19 releases
Affected
0.1.0 – 0.6.0
28 releases
What happens
Impact
When decoding user supplied MessagePack messages, users can trigger stuck threads by crafting messages that keep the decoder stuck in a loop.
Patches
The fix is available in v1.10.1
Workarounds
Exploits seem to require structured cloning, replacing the 0x70 extension with your own (that throws an error or does something other than recursive referencing) should mitigate the issue.
References
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.