Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learningUpgrade pillow to version 13.0.0 or higher.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via ImageFileDirectory_v2.load() in src/PIL/TiffImagePlugin.py, which reads the out-of-line value of every IFD entry into a separate bytes object stored in _tagdata without bounding the cumulative total across entries. An attacker can supply a TIFF, JPEG, PNG, WebP, or MPO file whose IFD entries each declare an offset and count that covers the entire file body, causing memory consumption proportional to N × file size - quadratic in the file size - because nothing prevents every entry from aliasing the same bytes. A 144 KB TIFF with 12,000 such entries causes Image.open() to retain 1.6 GiB of tag data with no exception or warning, since the image declares a 1×1 pixel size and the decompression-bomb check is never triggered. The same parser is reached from getexif() and ImageOps.exif_transpose() for PNG, JPEG, WebP, and MPO, and from Image.open() directly for TIFF and JPEG (via _read_dpi_from_exif()), so no additional API call is required to trigger the allocation.