Bug 1570188 (CVE-2018-10112) - CVE-2018-10112 gegl: write access violation in gegl_tile_backend_swap_constructed function in buffer/gegl-tile-backend-swap.c
Summary: CVE-2018-10112 gegl: write access violation in gegl_tile_backend_swap_constru...
Keywords:
Status: NEW
Alias: CVE-2018-10112
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1570186 1609102 1570189 1609101
Blocks: 1570194
TreeView+ depends on / blocked
 
Reported: 2018-04-20 20:35 UTC by Laura Pardo
Modified: 2020-12-21 04:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Laura Pardo 2018-04-20 20:35:30 UTC
A flaw was discovered in GEGL through 0.3.32. The gegl_tile_backend_swap_constructed function in buffer/gegl-tile-backend-swap.c allows remote attackers to cause a denial of service (write access violation) or possibly have unspecified other impact via a malformed PNG file that is mishandled during a call to the babl_format_get_bytes_per_pixel function in babl-format.c in babl 0.1.46.


References:
https://bugzilla.gnome.org/show_bug.cgi?id=795249
https://github.com/xiaoqx/pocs/tree/master/gegl

Comment 1 Laura Pardo 2018-04-20 20:36:52 UTC
Created gegl tracking bugs for this issue:

Affects: fedora-all [bug 1570186]

Comment 3 Doran Moppert 2018-07-27 02:53:33 UTC
Created gegl03 tracking bugs for this issue:

Affects: fedora-all [bug 1609102]

Comment 5 Debarshi Ray 2018-08-24 16:21:32 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.