Memory disclosure via unchecked FLI chunk parsing
Published Jun 25, 2020 · Updated Aug 4, 2024
Out-of-bounds reads in Pillow before 7.1.0 allow attackers to disclose process memory by supplying a crafted FLI image for decoding. ImagingFliDecode in libImaging/FliDecode.c parses SS2, LC, copy, and advance fields without checking that reads and copies remain within the encoded input buffer. A user or application must decode the malicious image; successful exploitation exposes data resident in the decoder process, with no demonstrated write or code-execution impact.
Summary
What happened
Out-of-bounds reads in Pillow before 7.1.0 allow attackers to disclose process memory by supplying a crafted FLI image for decoding. ImagingFliDecode in libImaging/FliDecode.c parses SS2, LC, copy, and advance fields without checking that reads and copies remain within the encoded input buffer. A user or application must decode the malicious image; successful exploitation exposes data resident in the decoder process, with no demonstrated write or code-execution impact.
The record
- CVE
- CVE-2020-10177
- Published
- Jun 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1204.002
- 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.
Public exploit references
No public exploit references are available in this record.
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