Bug 524671 (CVE-2008-1391) - CVE-2008-1391 glibc: strfmon format string problem
Summary: CVE-2008-1391 glibc: strfmon format string problem
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2008-1391
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://securityreason.com/achievement...
Whiteboard:
Depends On: 496386
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-21 16:59 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-24 07:16:51 UTC


Attachments (Terms of Use)

Description Jan Lieskovsky 2009-09-21 16:59:57 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2008-1391 to
the following vulnerability:

Multiple integer overflows in libc in NetBSD 4.x, FreeBSD 6.x and 7.x, and probably other BSD and Apple Mac OS platforms allow context-dependent attackers to execute arbitrary code via large values of certain integer fields in the format argument to (1) the strfmon function in lib/libc/stdlib/strfmon.c, related to the GET_NUMBER macro; and (2) the printf function, related to left_prec and right_prec.

References:
-----------
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1391
https://bugzilla.novell.com/show_bug.cgi?id=375315
http://www.securityfocus.com/bid/36443/references
http://securityreason.com/achievement_securityalert/67

Comment 2 Jan Lieskovsky 2009-09-21 17:06:06 UTC
Statement:

Red Hat does not consider this to be a security issue. Properly written
application should not use arbitrary untrusted data as part of the format
string passed to functions as strfmon or printf family functions.

Comment 5 Tomas Hoger 2011-02-04 19:11:40 UTC
glibc variants of this *BSD libc issues reported in SecurityReason Advisory 67 got separate CVE ids CVE-2009-4881 (bug #599095) and CVE-2009-4880 (bug #599070).


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