Service interruption via oversized FPX band count
Published Jan 5, 2020 · Updated Aug 5, 2024
Resource exhaustion in Pillow before 6.2.2 allows remote attackers to crash image-processing services with a crafted FPX image. FpxImagePlugin._open_index reads an unvalidated signed 32-bit band count from the file and passes it directly to range without rejecting values above four. An application must process an attacker-supplied FPX file; Linux 64-bit processes can be killed by the OOM killer, while Windows 32-bit Python raises memory-related exceptions.
Summary
What happened
Resource exhaustion in Pillow before 6.2.2 allows remote attackers to crash image-processing services with a crafted FPX image. FpxImagePlugin._open_index reads an unvalidated signed 32-bit band count from the file and passes it directly to range without rejecting values above four. An application must process an attacker-supplied FPX file; Linux 64-bit processes can be killed by the OOM killer, while Windows 32-bit Python raises memory-related exceptions.
The record
- CVE
- CVE-2019-19911
- Published
- Jan 5, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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