Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1579481 - (CVE-2018-10998) CVE-2018-10998 exiv2: SIGABRT by triggering an incorrect Safe::add call
CVE-2018-10998 exiv2: SIGABRT by triggering an incorrect Safe::add call
Status: NEW
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=20180509,reported=2...
: Security
Depends On: 1579489 1579983 1579485 1579486
Blocks: 1579499
  Show dependency treegraph
 
Reported: 2018-05-17 14:26 EDT by Laura Pardo
Modified: 2018-05-21 06:04 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Laura Pardo 2018-05-17 14:26:12 EDT
An issue was discovered in Exiv2 0.26. The readMetadata function in jp2image.cpp allows remote attackers to cause a denial of service (SIGABRT) by triggering an incorrect Safe::add call.


References:
https://github.com/Exiv2/exiv2/issues/303
Comment 1 Laura Pardo 2018-05-17 14:29:22 EDT
Created exiv2 tracking bugs for this issue:

Affects: fedora-all [bug 1579486]
Comment 6 Pedro Yóssis Silva Barbosa 2018-05-18 17:19:48 EDT
In RHEL 7, the PoC triggered a SIGABRT. Thus, this bug may have some deny of service effect (although not confirmed by upstream so far).
Comment 7 Pedro Yóssis Silva Barbosa 2018-05-21 06:04:05 EDT
The SIGABRT happens just because the exiv2 app is not catching an intended throwed exception.

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