Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1382006 - (CVE-2016-9190) CVE-2016-9190 python-pillow: Missing check for negative image dimensions in ImagingNew (Storage.c)
CVE-2016-9190 python-pillow: Missing check for negative image dimensions in I...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20161003,repor...
: Security
Depends On: 1380811
Blocks: 1382009
  Show dependency treegraph
 
Reported: 2016-10-05 09:51 EDT by Adam Mariš
Modified: 2016-12-11 21:06 EST (History)
5 users (show)

See Also:
Fixed In Version: python-pillow 3.3.2
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in python-pillow. A crafted image file with negative dimensions could cause a buffer to be under-allocated, leading to arbitrary writes on the heap which could cause a crash or, potentially, code execution.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-11 20:48:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-10-05 09:51:43 EDT
It was found that in storage.c, the image size is not checked for negative values. This can lead to a null pointer dereference in 3.3.x, or a dereference of junk memory prior to that.

Upstream patch:

https://github.com/python-pillow/Pillow/commit/5d8a0be45aad78c5a22c8d099118ee26ef8144af
Comment 1 Adam Mariš 2016-10-05 09:51:52 EDT
Acknowledgments:

Name: the Pillow project
Comment 3 Doran Moppert 2016-12-11 21:06:03 EST
Statement:

Red Hat Product Security has rated this issue as having Moderate security
impact. This issue is not currently planned to be addressed in future
updates. For additional information, refer to the Issue Severity
Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.