FreeImage 3.18.0 j2k.c j2k_read_ppm_v3 l_N_ppm out-of-bounds
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FreeImage 3.18.0. It has been classified as critical. Affected is the function j2k_read_ppm_v3
of the file j2k.c. The manipulation of the argument l_N_ppm leads to out-of-bounds.
This vulnerability is traded as CVE-2019-12214. It is possible to launch the attack remotely. There is no exploit available.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in FreeImage 3.18.0 and classified as critical. This issue affects the function j2k_read_ppm_v3
of the file j2k.c. The manipulation of the argument l_N_ppm
with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In FreeImage 3.18.0, an out-of-bounds access occurs because of mishandling of the OpenJPEG j2k_read_ppm_v3 function in j2k.c. The value of l_N_ppm comes from the file read in, and the code does not consider that l_N_ppm may be greater than the size of p_header_data.
The bug was discovered 05/19/2019. The weakness was published 05/20/2019. The identification of this vulnerability is CVE-2019-12214 since 05/20/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-135274, VDB-135273 and VDB-135272. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/19/2019 🔍05/20/2019 🔍
05/20/2019 🔍
05/21/2019 🔍
09/23/2023 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
CVE: CVE-2019-12214 (🔍)
GCVE (CVE): GCVE-0-2019-12214
GCVE (VulDB): GCVE-100-135275
See also: 🔍
Entry
Created: 05/21/2019 07:36 AMUpdated: 09/23/2023 09:45 AM
Changes: 05/21/2019 07:36 AM (55), 06/13/2020 11:17 PM (1), 09/23/2023 09:45 AM (3)
Complete: 🔍
Cache ID: 18:BE4:40
No comments yet. Languages: en.
Please log in to comment.