msgpack5: Truncated map32 headers throw an unexpected error

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

• msgpack5 6.1.0Fixed version · GitHub Advisories · npm package msgpack5: upgrade to 6.1.0 or later (affected >= 4.1.0, < 6.1.0)

[ Packages ]Affected open-source packages

• msgpack5 npmAffected >= 4.1.0, < 6.1.0 · fixed in 6.1.0 · GHSA-8f34-f56x-9xph

[ References ]References

• github.com/mcollina/msgpack5/commit/15443a1f2aa682a6aa37f1705ac628de5b866ad1
• github.com/mcollina/msgpack5/releases/tag/v6.1.0
• github.com/mcollina/msgpack5/security/advisories/GHSA-8f34-f56x-9xph