Bug 951257 - (CVE-2013-1953) CVE-2013-1953 autotrace: buffer overflow when parsing BMP files
CVE-2013-1953 autotrace: buffer overflow when parsing BMP files
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20130416,reported=2...
: Security
Depends On: 952668 979244
Blocks: 951258
  Show dependency treegraph
 
Reported: 2013-04-11 16:46 EDT by Vincent Danen
Modified: 2015-08-22 03:00 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-22 03:00:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Proposed fix sent upstream (603 bytes, patch)
2013-06-28 04:26 EDT, Jaroslav Škarvada
no flags Details | Diff

  None (edit)
Description Vincent Danen 2013-04-11 16:46:39 EDT
A buffer overflow flaw was reported in autotrace's input_bmp_reader() function.  When autotrace is compiled with FORTIFY_SOURCE, this is caught and turned into a simple denial of service.  As reported:

In input-bmp.c, the input_bmp_reader() function creates a buffer on the 
stack:

91 unsigned char buffer[64];

Later on

169 else if (Bitmap_File_Head.biSize <= 64) /* Probably OS/2 2.x */
170 {
171 if (!ReadOK (fd, buffer, Bitmap_File_Head.biSize - 4))

We control Bitmap_File_Head.biSize. A value of 0 meets the <=64 
requirements, and 0 - 4 should result in almost 4294967295 bytes being 
read into the buffer.
Comment 1 Vincent Danen 2013-04-12 01:05:00 EDT
Acknowledgements:

This issue was discovered by Murray McAllister of Red Hat Security Response Team.
Comment 2 Jan Lieskovsky 2013-04-16 08:00:52 EDT
The CVE identifier of CVE-2013-1953 has been assigned to this issue:
  http://www.openwall.com/lists/oss-security/2013/04/16/3
Comment 3 Jan Lieskovsky 2013-04-16 08:03:15 EDT
Created autotrace tracking bugs for this issue

Affects: fedora-all [bug 952668]
Comment 5 Jaroslav Škarvada 2013-06-28 04:26:45 EDT
Created attachment 766451 [details]
Proposed fix sent upstream
Comment 6 Fedora Update System 2013-07-08 21:40:38 EDT
autotrace-0.31.1-34.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 7 Fedora Update System 2013-07-08 21:41:14 EDT
autotrace-0.31.1-34.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.