bincookie: Heap buffer overflow via unvalidated `num_pages` when parsing a `.binarycookies` file
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Tatsh | bincookie | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tatsh | Bincookie |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.222% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tatsh
Tatsh bincookie |
|
| Vendors & Products |
Tatsh
Tatsh bincookie |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | bincookie is a header-only binarycookies parser. Prior to 0.1.9, bincookie_init_file() in bincookie.h allocates a buffer using the actual .binarycookies file length but trusts the file-controlled num_pages field as the loop bound for byte-swapping page_sizes entries. A crafted file can make the loop read and write beyond the heap allocation, and related unvalidated page sizes and cookie_offsets can drive additional out-of-bounds accesses in page and cookie iteration. Applications that parse an attacker-supplied binarycookies file may crash or suffer heap corruption that can potentially enable code execution. This issue is fixed in version 0.1.9. | |
| Title | bincookie: Heap buffer overflow via unvalidated `num_pages` when parsing a `.binarycookies` file | |
| Weaknesses | CWE-122 CWE-787 |
|
| References |
| |
| Metrics |
cvssV3_1
|