libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| libjxl | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Libjxl | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.111% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libjxl Project
Libjxl Project libjxl |
|
| CPEs | cpe:2.3:a:libjxl_project:libjxl:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Libjxl Project
Libjxl Project libjxl |
|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-125 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google libjxl |
|
| Vendors & Products |
Google
Google libjxl |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory. This can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to omit populating those areas. | |
| Title | libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling | |
| Weaknesses | CWE-908 | |
| References |
| |
| Metrics |
cvssV4_0
|