Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1133306 - (CVE-2014-3606) CVE-2014-3606 python-pillow: flaw in _unop()
CVE-2014-3606 python-pillow: flaw in _unop()
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Red Hat Product Security
impact=none,public=20141112,reported=...
: Security
Depends On:
Blocks: 1133307
  Show dependency treegraph
 
Reported: 2014-08-24 09:49 EDT by Murray McAllister
Modified: 2015-08-19 04:36 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-11-12 04:17:28 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 Murray McAllister 2014-08-24 09:49:10 EDT
A flaw was found in the _unop() function in python-pillow's math add-on. A specially-crafted image could cause an application using Python Pillow to crash or, potentially, execute arbitrary code.

Acknowledgements:

This issue was discovered by Francisco Alonso of Red Hat Product Security.
Comment 8 Tomas Hoger 2014-11-12 04:51:49 EST
This issue was found while fuzzing PIL/pillow.  A specially crafted arguments passed to _imagingmath.unop() trigger crash in the native code of the library.

The _imagingmath is an internal helper module used by the ImageMath module, that is not meant to be used directly.  The unop() function uses its arguments as pointers, even a function pointer in case of its first argument.  Any use case where its called with untrusted arguments would allow code execution.

However, that's not how unop() is used in ImageMath, which properly constructs arguments for the function.  Contrary to the information in comment 0, observed crash is not triggered by a specially-crafted image, but rather caused by an incorrect function use.

Hence this is not a security issue.

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