Skip to content
Fencer Intel
medium 6.9

CVE-2011-4355 json

GNU Project Debugger (GDB) before 7.5, when .debug_gdb_scripts is defined, automatically loads certain files from the current working direc…

published 2013-03-04 13 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4286

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

GNU Project Debugger (GDB) before 7.5, when .debug_gdb_scripts is defined, automatically loads certain files from the current working directory, which allows local users to gain privileges via crafted files such as Python scripts.

Patch / fix

  • gdb Debian 14, Debian 13, Debian 12 7.6-1

debian advisories DEBIAN-CVE-2011-4355

  • gdb RHEL 6 7.2-60.el6
  • gdb-gdbserver RHEL 6 7.2-60.el6

red hat advisories RHSA-2013:0522

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-4355 updated cvss 3.7

gdb: object file .debug_gdb_scripts section improper input validation

  • Red Hat Enterprise Linux 4 gdb Red Hat Enterprise Linux 5 gdb
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Desktop (v. 6) gdb 7.2-60.el6, gdb-gdbserver 7.2-60.el6 Red Hat Enterprise Linux HPC Node (v. 6) gdb 7.2-60.el6, gdb-gdbserver 7.2-60.el6 Red Hat Enterprise Linux Server (v. 6) gdb 7.2-60.el6, gdb-gdbserver 7.2-60.el6 Red Hat Enterprise Linux Workstation (v. 6) gdb 7.2-60.el6, gdb-gdbserver 7.2-60.el6
    fixed: vendor fix RHSA-2013:0522

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.