Mcollina msgpack5
msgpack5: Truncated map32 headers throw an unexpected error
msgpack5 is a msgpack v5 implementation for node.js and the browser. Prior to 6.1.0, the decoder reads the four-byte length of a map32 value before validating that the complete five-byte header is available. A truncated map32 header therefore causes a checked out-of-bounds buffer read and throws RangeError instead of IncompleteBufferError, which can unexpectedly terminate a request, stream, or worker in applications that wait for additional bytes after IncompleteBufferError. There is no adjacent-memory disclosure because the buffer implementation checks bounds. This issue is fixed in version 6.1.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.1.0. < 6.1.0
Fixed in 6.1.0
Mitigation
Upgrade msgpack5 to 6.1.0 or later.
References
- Vendor advisory github.com/mcollina/msgpack5/security/advisori…
- Patch github.com/mcollina/msgpack5/commit/15443a1f2a…
- Release notes github.com/mcollina/msgpack5/releases/tag/v6.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.