Bug 171825

Summary: CAN-2005-1704 Integer overflow in gdb
Product: [Fedora] Fedora Reporter: Jeff Johnston <jjohnstn>
Component: gdbAssignee: Jeff Johnston <jjohnstn>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 3CC: cagney, jakub, jan.kratochvil, jjohnstn, mattdm
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,public=20050525,reported=20050504,source=vendorsec
Fixed In Version: gdb-6.1post-1.20040607.43.0.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-14 17:10:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Johnston 2005-10-26 20:38:25 UTC
Integer overflow in the BFD library for gdb before 6.3 allows
attackers to execute arbitrary code via a crafted object file that
specifies a large number of section headers, leading to a heap-based
buffer overflow.


More information is available in the gentoo bug:
http://bugs.gentoo.org/show_bug.cgi?id=91398

-

Comment 1 Jeff Johnston 2005-10-26 20:56:31 UTC
Fixed in gdb-6.1post-1.20040607.43.0.1

Comment 2 Fedora Update System 2005-10-27 17:08:18 UTC
From User-Agent: XML-RPC

gdb-6.1post-1.20040607.43.0.1 has been pushed for FC3, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 3 Matthew Miller 2006-07-10 23:05:20 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 4 Jan Kratochvil 2007-01-14 17:10:08 UTC
Already processed a long time ago and fixed according to Comment 1.