Code execution via oversized JPEG dimension loops
Published Mar 16, 2020 · Updated Aug 5, 2024
Heap-based buffer overflow in GNOME gThumb before 3.8.3 and Linux Mint Pix before 2.4.5 allows attackers to execute code via a crafted JPEG. The JPEG loader caps dimensions when allocating a Cairo surface but loops over the uncapped dimensions when copying pixels, writing beyond the surface buffer. The user must open the file; the overwrite crashes the viewer or executes attacker-controlled code with the process's privileges.
Summary
What happened
Heap-based buffer overflow in GNOME gThumb before 3.8.3 and Linux Mint Pix before 2.4.5 allows attackers to execute code via a crafted JPEG. The JPEG loader caps dimensions when allocating a Cairo surface but loops over the uncapped dimensions when copying pixels, writing beyond the surface buffer. The user must open the file; the overwrite crashes the viewer or executes attacker-controlled code with the process's privileges.
The record
- CVE
- CVE-2019-20326
- Published
- Mar 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Fysac crafted JPEG proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo