MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| msgpack | msgpack-ruby | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Msgpack | Msgpack |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4mrv-5p47-p938 | MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.227% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Msgpack
Msgpack msgpack |
|
| Vendors & Products |
Msgpack
Msgpack msgpack |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MessagePack for Ruby is an implementation of the MessagePack binary serialization format. Prior to 1.8.2, MessagePack::Buffer#clear in ext/msgpack/buffer.c leaves rmem_last, rmem_end, and rmem_owner stale after _msgpack_buffer_shift_chunk returns an rmem page to the shared pool, allowing a subsequent Buffer#write and a second MessagePack::Buffer to alias the page and disclose or corrupt cross-buffer data. This issue is fixed in version 1.8.2. | |
| Title | MessagePack::Buffer#clear Use-After-Free that Enables Cross-Buffer Disclosure | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV4_0
|