Vulnerability Assessment & Network Security Forums



If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important.  If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.


Home >> Browse Vulnerability Assessment Database >> Red Hat Local Security Checks >> RHSA-2005-709: gdb


Vulnerability Assessment Details

RHSA-2005-709: gdb

Vulnerability Assessment Summary
Check for the version of the gdb packages

Detailed Explanation for this Vulnerability Assessment


An updated gdb package that fixes several bugs and minor security issues is
now available.

This update has been rated as having low security impact by the Red Hat
Security Response Team.

GDB, the GNU debugger, permits debugging of programs written in C, C++,
and other languages by executing them in a controlled fashion, then
printing their data.

Several integer overflow bugs were found in gdb. If a user is tricked
into processing a specially crafted executable file, it may permit the
execution of arbitrary code as the user running gdb. The Common
Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name
CVE-2005-1704 to this issue.

A bug was found in the way gdb loads .gdbinit files. When a user executes
gdb, the local directory is searched for a .gdbinit file which is then
loaded. It is possible for a local user to execute arbitrary commands as
the victim running gdb by placing a malicious .gdbinit file in a location
where gdb may be run. The Common Vulnerabilities and Exposures project
(cve.mitre.org) has assigned the name CVE-2005-1705 to this issue.

This updated package also addresses the following issues:

- GDB on ia64 had previously implemented a bug fix to work-around a kernel
problem when creating a core file via gcore. The bug fix caused a
significant slow-down of gcore.

- GDB on ia64 issued an extraneous warning when gcore was used.

- GDB on ia64 could not backtrace over a sigaltstack.

- GDB on ia64 could not successfully do an info frame for a signal
trampoline.

- GDB on AMD64 and Intel EM64T had problems attaching to a 32-bit process.

- GDB on AMD64 and Intel EM64T was not properly handling threaded
watchpoints.

- GDB could not build with gcc4 when -Werror flag was set.

- GDB had problems printing inherited members of C++ classes.

- A few updates from mainline sources concerning Dwarf2 partial die in
cache support, follow-fork support, interrupted syscall support, and
DW_OP_piece read support.

All users of gdb should upgrade to this updated package, which resolves
these issues.




Solution : http://rhn.redhat.com/errata/RHSA-2005-709.html
Network Security Threat Level: High

Networks Security ID:

Vulnerability Assessment Copyright: This script is Copyright (C) 2005 Tenable Network Security

Cables, Connectors

Cooler Master Hyper 212 Evo CPU Cooler
$15.0
Cooler Master Hyper 212 Evo CPU Cooler pictureHP Chromebook 11 G4 Intel 2.16ghz CPU 11.6" Display 2GB Ram 16GB HD HDMI USB M36
$140.0
HP Chromebook 11 G4 Intel 2.16ghz CPU 11.6Intel Core i5-4570S 2.9GHz up to 3.6GHz SR14J LGA1150 Haswell CPU
$125.0
Intel Core i5-4570S 2.9GHz up to 3.6GHz SR14J LGA1150 Haswell CPU picturePentium 4 double strike stamp error CPU (RARE) Collector's Item L@@K
$500.0
Pentium 4 double strike stamp error CPU (RARE) Collector's Item L@@K picture


Discussions

No Discussions have been posted on this vulnerability.