Affected version: 6.x up to and including 6.2.1
Vendor status: Fixed version released (6.2.2)
Remote exploitation of a heap overflow vulnerability could allow execution of
arbitrary code or couse denial of service.
graphics please advise.
*** Bug 90479 has been marked as a duplicate of this bug. ***
Bumped to 22.214.171.124 in portage
Arches please test and mark stable.
Note that Perlmagick is now part of Imagemagick so you only need to mark one package stable.
stable on ppc64
Stable on alpha + ia64.
Stable on amd64
Apparently this is not exploitable to execute code so it might be declassified from vulnerability to a simple bug. Waiting as our auditors are busy scouting the code for exploitable ones.
Shouldn't the imagemagick ebuild block (using DEPEND) perlmagick instead of doing it in pkg_setup() ??
stable on x86
tester: we want to inform users about this change, perlmagick will be soon removed from portage.
Stable on hppa.
Imagemagick should block perlmagick in DEPEND not pkg_setup().
See comment 10.
iirc, the logic was that we wanted to be able to explain why it was blocked (ie, via some nice ewarns) than merely to show up with a B and no explanation.
Taviso/tigger any news on this one?
There are a few crashes, but nothing that looks serious yet. There is a DoS in the xwd decoder:
in this loop, the mask is set in the image and can be set to zero:
347 Determine shift and mask for red, green, and blue.
351 while ((red_mask & 0x01) == 0)
(and the same below for green and blue), which could potentially be a nuisance for web-apps or similar that rely on im for image processing.
Arches please mark stable.
Created attachment 58154 [details]
xwd DoS testcase
testcase for XWD DoS.
As I understand it, this is NOT fixed by the current release -> back to upstream status.
Btw: Taviso, has upstream been notified?
PNM Heap overflow is being re-classified as a non-security bug, remaining issue is the xwd DoS.
XWD DoS issue fixed in upstream 6.2.2-3
graphics team, please bump
imagemagick-126.96.36.199 in portage
Arches, please test and mark stable
Target KEYWORDS="alpha amd64 hppa ia64 ~mips ppc ppc64 sparc x86"
Stable on ppc. (it even fixes those funny colors with import!)
Stable on hppa
stable on amd64
on x86, I get a sigfpe with the attached test.xwd.. that does not feel ok to me..
SPARC me like a hurricane
Karol please see comment #29
btw, I get the same result on amd64 as comment #29
The security bug was that processing the testcase image would eat your CPU for a
few minutes. If it just crashes, it's no longer an issue... That said, I thought
that using Tavis patch it would fail more nicely.
[09:26:46] <@taviso> jaervosz: it wasnt my patch, i just reported the issue and suggested catching the condition..that's how upstream fixed it :) sigfpe isnt a security problem, no different from feeding it an invalid image.
Not that its a good fix.. but I'm marking stable anyway ;)
Ready for a combined GLSA with graphicsmagick