CVE-2022-37768 json
libjpeg commit 281daa9 was discovered to contain an infinite loop via the component Frame::ParseTrailer.
published 4y ago modified 4mo ago also EUVD-2022-40378
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
libjpeg commit 281daa9 was discovered to contain an infinite loop via the component Frame::ParseTrailer.
Patch / fix
- jpeg libjpeg 9f
- libjpeg Debian 14, Debian 13, Debian 12 0.0~git20220805.54ec643-1
debian advisories DEBIAN-CVE-2022-37768
Is CVE-2022-37768 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/thorfdbg/libjpeg/issues/77 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
github.com
/thorfdbg/libjpeg/issues/77
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2022-37768
- NVD CVE-2022-37768
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Update CPE details.