libjpeg: improper handling of max_memory_to_use setting can lead to excessive memory consumption
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2302-1 | libjpeg-turbo security update |
EUVD |
EUVD-2020-6309 | In IJG JPEG (aka libjpeg) before 9d, jpeg_mem_available() in jmemnobs.c in djpeg does not honor the max_memory_to_use setting, possibly causing excessive memory consumption. |
Ubuntu USN |
USN-5336-1 | libjpeg9 vulnerabilities |
Ubuntu USN |
USN-5497-1 | Libjpeg6b vulnerabilities |
Ubuntu USN |
USN-5497-2 | Libjpeg6b vulnerabilities |
Ubuntu USN |
USN-5553-1 | libjpeg-turbo vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.488% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.