Service crash via negative TIFF read size
Published Mar 19, 2021 · Updated Aug 3, 2024
Buffer overflow in Pillow before 8.1.1 allows remote attackers to crash image-processing services by supplying a crafted TIFF image. _tiffReadProc in TiffDecode.c subtracts a stream location beyond the end of file, producing a negative copy length for memcpy. The application must decode attacker-supplied TIFF data; successful exploitation interrupts the processing service without reported data disclosure or modification.
Summary
What happened
Buffer overflow in Pillow before 8.1.1 allows remote attackers to crash image-processing services by supplying a crafted TIFF image. _tiffReadProc in TiffDecode.c subtracts a stream location beyond the end of file, producing a negative copy length for memcpy. The application must decode attacker-supplied TIFF data; successful exploitation interrupts the processing service without reported data disclosure or modification.
The record
- CVE
- CVE-2021-25290
- Published
- Mar 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Public exploit references
- Pillow TIFF crash regression corpusproof 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