Bug 1570191 (CVE-2018-10113) - CVE-2018-10113 gegl: unbounded memory allocation in process function in operations/external/ppm-load.c
Summary: CVE-2018-10113 gegl: unbounded memory allocation in process function in opera...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-10113
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1570186 1570189 1609103 1609104
Blocks: 1570194
TreeView+ depends on / blocked
 
Reported: 2018-04-20 20:42 UTC by Laura Pardo
Modified: 2021-10-21 20:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 20:02:25 UTC
Embargoed:

Attachments (Terms of Use)

Description Laura Pardo 2018-04-20 20:42:28 UTC 
A flaw was discovered in GEGL through 0.3.32. The process function in operations/external/ppm-load.c has unbounded memory allocation, leading to a denial of service (application crash) upon allocation failure.


References:
https://github.com/xiaoqx/pocs/tree/master/gegl
Comment 1 Laura Pardo 2018-04-20 20:44:01 UTC 
Created gegl tracking bugs for this issue:

Affects: fedora-all [bug 1570186]
Comment 3 Doran Moppert 2018-07-27 02:53:37 UTC 
Created gegl03 tracking bugs for this issue:

Affects: fedora-all [bug 1609104]
Comment 5 Debarshi Ray 2018-08-24 16:23:18 UTC 
As an upstream contributor to GEGL, and a downstream Fedora packager, I am surprised that this managed to bubble all the way up to becoming a CVE!

As far as I can make out, this was originally filed as https://bugzilla.gnome.org/show_bug.cgi?id=795249, which got migrated to https://gitlab.gnome.org/GNOME/gegl/issues/65 Note the complete lack of response from the reporter after the initial submission. Anyway, I have added a comment to the Gitlab issue that should clarify the situation a bit more.

In short, this is a known problem that's being worked on. It's not possible to fix it with a small localized fix that can be carried downstream.
Note You need to log in before you can comment on or make changes to this bug.