Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1418147 - (CVE-2016-9112) CVE-2016-9112 openjpeg2: Floating point exception vulnerability in openjpeg2 when processing untrusted images
CVE-2016-9112 openjpeg2: Floating point exception vulnerability in openjpeg2 ...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20170201,reported=2...
: Security
Depends On: 1418149 1418150 1418151 1418152
Blocks: 1374338
  Show dependency treegraph
 
Reported: 2017-01-31 21:25 EST by Doran Moppert
Modified: 2017-01-31 22:11 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-31 22:11:16 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 Doran Moppert 2017-01-31 21:25:53 EST
A floating point exception vulnerability was found in the latest openjpeg2.  A maliciously crafted file could cause the application to crash.

This issue has multiple occurrences in the openjpeg2 code.

openjpeg-1 is also affected.

Upstream bug:

https://github.com/uclouvain/openjpeg/issues/855
Comment 1 Doran Moppert 2017-01-31 21:44:12 EST
Created mingw-openjpeg tracking bugs for this issue:

Affects: fedora-all [bug 1418151]


Created openjpeg tracking bugs for this issue:

Affects: fedora-all [bug 1418149]


Created openjpeg2 tracking bugs for this issue:

Affects: epel-all [bug 1418152]
Affects: fedora-all [bug 1418150]
Comment 2 Doran Moppert 2017-01-31 22:10:45 EST
Statement:

Red Hat Product Security has rated this issue as having Low 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.