Memory corruption via undersized TIFF decode buffers
Published Jun 25, 2020 · Updated Aug 4, 2024
Buffer overflows in Pillow before 7.1.0 allow context-dependent attackers to corrupt memory by supplying crafted TIFF images. The TIFF decoder sized state->buffer from image row and tile dimensions without ensuring that the allocation accommodated libtiff's decoded tile or strip size. An application must load attacker-supplied TIFF content; the resulting out-of-bounds write can crash the consuming process or corrupt its memory.
Summary
What happened
Buffer overflows in Pillow before 7.1.0 allow context-dependent attackers to corrupt memory by supplying crafted TIFF images. The TIFF decoder sized state->buffer from image row and tile dimensions without ensuring that the allocation accommodated libtiff's decoded tile or strip size. An application must load attacker-supplied TIFF content; the resulting out-of-bounds write can crash the consuming process or corrupt its memory.
The record
- CVE
- CVE-2020-10379
- Published
- Jun 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
- Pillow TIFF crash reproducer imagesproof 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