This bug was fixed in the package gimp - 2.8.22-1
---
gimp (2.8.22-1) unstable; urgency=medium
* New upstream release (Closes: #870568, #885382, CVE-2007-3126)
(LP: #1690544)
* Switch maintainer to Debian GNOME Team, with Ari's permission
* Update Vcs fields for migration
This will be updated in Ubuntu 18.04 "bionic" via sync from Debian.
** Changed in: gimp (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690544
Title:
As I wrote in https://bugzilla.gnome.org/show_bug.cgi?id=773233#c2
(that's the bug for the master branch, where GIMP 2.9.x is being made
from), I could not reproduce the crash mentioned in the CVE. Probably no
surprise, given that CVE was reported against GIMP 2.3.x
However, I'd like to stress
** Changed in: gimp
Status: Unknown => Fix Released
** Changed in: gimp
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690544
Title:
include proper fix for
** Bug watch added: GNOME Bug Tracker #778604
https://bugzilla.gnome.org/show_bug.cgi?id=778604
** Also affects: gimp via
https://bugzilla.gnome.org/show_bug.cgi?id=778604
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2007-3126
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690544
Title:
include proper fix for CVE-2007-3126, released in GIMP 2.8.22
