libjpeg 281daa9 File huffmandecoder.hpp HuffmanDecoder::Get memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in libjpeg 281daa9. Impacted is the function HuffmanDecoder::Get of the file huffmandecoder.hpp of the component File Handler. Performing a manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2022-37769. It is possible to initiate the attack remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as critical has been found in libjpeg 281daa9. This affects the function HuffmanDecoder::Get of the file huffmandecoder.hpp of the component File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
libjpeg commit 281daa9 was discovered to contain a segmentation fault via HuffmanDecoder::Get at huffmandecoder.hpp. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file.
The weakness was shared 08/19/2022 as 78. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-37769 since 08/08/2022. 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 pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/19/2022).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
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
08/08/2022 🔍08/19/2022 🔍
08/19/2022 🔍
08/19/2022 🔍
Sources
Advisory: 78Status: Confirmed
CVE: CVE-2022-37769 (🔍)
GCVE (CVE): GCVE-0-2022-37769
GCVE (VulDB): GCVE-100-206739
Entry
Created: 08/19/2022 07:45 AMChanges: 08/19/2022 07:45 AM (40)
Complete: 🔍
Cache ID: 244:B88:40
No comments yet. Languages: en.
Please log in to comment.