Bug 1172642 (CVE-2020-13902) - VUL-1: CVE-2020-13902: ImageMagick: heap-based buffer over-read in BlobToStringInfo in MagickCore/string.c during TIFF image decoding
Summary: VUL-1: CVE-2020-13902: ImageMagick: heap-based buffer over-read in BlobToStri...
Status: RESOLVED WORKSFORME
Alias: CVE-2020-13902
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P4 - Low : Minor
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/260890/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-08 08:08 UTC by Wolfgang Frisch
Modified: 2020-06-16 15:51 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Frisch 2020-06-08 08:08:19 UTC 
CVE-2020-13902

ImageMagick 7.0.9-27 through 7.0.10-17 has a heap-based buffer over-read in
BlobToStringInfo in MagickCore/string.c during TIFF image decoding.

References:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=20920
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-13902
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13902
Comment 1 Petr Gajdos 2020-06-08 13:54:16 UTC 
Do you know the command to reproduce?

I am sorry, but I do not see how the link to oss-fuzz could help me. I tried several commands over the testcase with 7.0.10-17 built with asan. None of them led to the asan report, though.
Comment 3 Wolfgang Frisch 2020-06-16 15:51:52 UTC 
(In reply to Petr Gajdos from comment #1)
> Do you know the command to reproduce?
> 
> I am sorry, but I do not see how the link to oss-fuzz could help me. I tried
> several commands over the testcase with 7.0.10-17 built with asan. None of
> them led to the asan report, though.
Yes, unfortunately I was not able to reproduce the issue with various versions of ImageMagick either.

(In reply to Petr Gajdos from comment #2)
> https://github.com/ImageMagick/ImageMagick/discussions/2132

And this indeed explains why. The change in the tiff library [1], that triggers the problem, is not present in any of our code streams.

We're not affected.

[1] https://gitlab.com/libtiff/libtiff/-/merge_requests/99