Bug 1366239 (CVE-2016-6328) - CVE-2016-6328 libexif: Integer overflow in parsing MNOTE entry data of the input file
Summary: CVE-2016-6328 libexif: Integer overflow in parsing MNOTE entry data of the in...
Alias: CVE-2016-6328
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1484032
Blocks: 1366243
TreeView+ depends on / blocked
Reported: 2016-08-11 11:07 UTC by Andrej Nemec
Modified: 2021-06-03 15:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-22 13:32:03 UTC

Attachments (Terms of Use)

Description Andrej Nemec 2016-08-11 11:07:25 UTC
A vulnerability was found in libexif. The vulnerability is caused by an integer overflow. In some cases, the integer overflow can cause Heap Out-of-Bounds Read, i.e. Heap Buffer Overflow vulnerability. In some others cases, the integer overflow can cause use of uninitialized pointer variable, i.e. Use of Uninitialized Variable Vulnerability. The vulnerability happens when parsing MNOTE entry data of the input file. The vulnerability can cause Denial-of-Service (DoS) and Information Disclosure (disclosing some critical heap chunk metadata, even other applications’ private data).

Comment 9 Stefan Cornelius 2017-08-22 13:31:09 UTC

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/.

Comment 10 Stefan Cornelius 2017-08-22 13:32:29 UTC
Created libexif tracking bugs for this issue:

Affects: fedora-all [bug 1484032]

Comment 11 Yaakov Selkowitz 2017-12-15 20:52:37 UTC
(In reply to Stefan Cornelius from comment #8)
> Patch:
> http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/libexif/pentax/
> mnote-pentax-entry.c?r1=1.26&r2=1.27

Or in its new location:


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