ID CVE-2011-4355
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.
References
Vulnerable Configurations
  • GNU GNU Debugger GDB 7.4.1
    cpe:2.3:a:gnu:gdb:7.4.1
  • GNU GNU Debugger GDB 7.4
    cpe:2.3:a:gnu:gdb:7.4
  • GNU GNU Debugger GDB 7.3.1
    cpe:2.3:a:gnu:gdb:7.3.1
  • GNU GNU Debugger GDB 7.3
    cpe:2.3:a:gnu:gdb:7.3
  • GNU GNU Debugger GDB 7.2
    cpe:2.3:a:gnu:gdb:7.2
  • GNU GNU Debugger GDB 7.1
    cpe:2.3:a:gnu:gdb:7.1
  • GNU GNU Debugger GDB 7.0.1
    cpe:2.3:a:gnu:gdb:7.0.1
  • GNU GNU Debugger GDB 7.0
    cpe:2.3:a:gnu:gdb:7.0
  • GNU GNU Debugger GDB 6.8
    cpe:2.3:a:gnu:gdb:6.8
  • GNU GNU Debugger GDB 6.7.1
    cpe:2.3:a:gnu:gdb:6.7.1
  • GNU GNU Debugger GDB 6.7
    cpe:2.3:a:gnu:gdb:6.7
  • GNU GNU Debugger GDB 6.6
    cpe:2.3:a:gnu:gdb:6.6
  • GNU GNU Debugger GDB 6.5
    cpe:2.3:a:gnu:gdb:6.5
  • GNU GNU Debugger GDB 6.4
    cpe:2.3:a:gnu:gdb:6.4
  • GNU GNU Debugger GDB 6.3
    cpe:2.3:a:gnu:gdb:6.3
  • GNU GNU Debugger GDB 6.2.1
    cpe:2.3:a:gnu:gdb:6.2.1
  • GNU GNU Debugger GDB 6.2
    cpe:2.3:a:gnu:gdb:6.2
  • GNU GNU Debugger GDB 6.1.1
    cpe:2.3:a:gnu:gdb:6.1.1
  • GNU GNU Debugger GDB 6.1
    cpe:2.3:a:gnu:gdb:6.1
  • GNU GNU Debugger GDB 6.0
    cpe:2.3:a:gnu:gdb:6.0
  • GNU GNU Debugger GDB 5.3
    cpe:2.3:a:gnu:gdb:5.3
  • GNU GNU Debugger GDB 5.2.1
    cpe:2.3:a:gnu:gdb:5.2.1
  • GNU GNU Debugger GDB 5.2
    cpe:2.3:a:gnu:gdb:5.2
  • GNU GNU Debugger GDB 5.1.1
    cpe:2.3:a:gnu:gdb:5.1.1
  • GNU GNU Debugger GDB 5.1
    cpe:2.3:a:gnu:gdb:5.1
  • GNU GNU Debugger GDB 5.0.93
    cpe:2.3:a:gnu:gdb:5.0.93
  • GNU GNU Debugger GDB 5.0.92
    cpe:2.3:a:gnu:gdb:5.0.92
  • GNU GNU Debugger GDB 5.0
    cpe:2.3:a:gnu:gdb:5.0
  • GNU GNU Debugger GDB 4.18
    cpe:2.3:a:gnu:gdb:4.18
CVSS
Base: 6.9 (as of 06-03-2013 - 08:25)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
LOCAL MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
nessus via4
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20130221_GDB_ON_SL6_X.NASL
    description GDB tried to auto-load certain files (such as GDB scripts, Python scripts, and a thread debugging library) from the current working directory when debugging programs. This could result in the execution of arbitrary code with the user's privileges when GDB was run in a directory that has untrusted content. (CVE-2011-4355) With this update, GDB no longer auto-loads files from the current directory and only trusts certain system directories by default. The list of trusted directories can be viewed and modified using the 'show auto-load safe-path' and 'set auto-load safe-path' GDB commands. Refer to the GDB manual, linked to in the References, for further information. This update also fixes the following bugs : - When a struct member was at an offset greater than 256 MB, the resulting bit position within the struct overflowed and caused an invalid memory access by GDB. With this update, the code has been modified to ensure that GDB can access such positions. - When a thread list of the core file became corrupted, GDB did not print this list but displayed the 'Cannot find new threads: generic error' error message instead. With this update, GDB has been modified and it now prints the thread list of the core file as expected. - GDB did not properly handle debugging of multiple binaries with the same build ID. This update modifies GDB to use symbolic links created for particular binaries so that debugging of binaries that share a build ID now proceeds as expected. Debugging of live programs and core files is now more user-friendly.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 64951
    published 2013-03-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=64951
    title Scientific Linux Security Update : gdb on SL6.x i386/x86_64
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2013-0522.NASL
    description Updated gdb packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The GNU Debugger (GDB) allows debugging of programs written in C, C++, Java, and other languages by executing them in a controlled fashion and then printing out their data. GDB tried to auto-load certain files (such as GDB scripts, Python scripts, and a thread debugging library) from the current working directory when debugging programs. This could result in the execution of arbitrary code with the user's privileges when GDB was run in a directory that has untrusted content. (CVE-2011-4355) With this update, GDB no longer auto-loads files from the current directory and only trusts certain system directories by default. The list of trusted directories can be viewed and modified using the 'show auto-load safe-path' and 'set auto-load safe-path' GDB commands. Refer to the GDB manual, linked to in the References, for further information. This update also fixes the following bugs : * When a struct member was at an offset greater than 256 MB, the resulting bit position within the struct overflowed and caused an invalid memory access by GDB. With this update, the code has been modified to ensure that GDB can access such positions. (BZ#795424) * When a thread list of the core file became corrupted, GDB did not print this list but displayed the 'Cannot find new threads: generic error' error message instead. With this update, GDB has been modified and it now prints the thread list of the core file as expected. (BZ#811648) * GDB did not properly handle debugging of multiple binaries with the same build ID. This update modifies GDB to use symbolic links created for particular binaries so that debugging of binaries that share a build ID now proceeds as expected. Debugging of live programs and core files is now more user-friendly. (BZ#836966) All users of gdb are advised to upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 64769
    published 2013-02-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=64769
    title RHEL 6 : gdb (RHSA-2013:0522)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2013-0522.NASL
    description Updated gdb packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The GNU Debugger (GDB) allows debugging of programs written in C, C++, Java, and other languages by executing them in a controlled fashion and then printing out their data. GDB tried to auto-load certain files (such as GDB scripts, Python scripts, and a thread debugging library) from the current working directory when debugging programs. This could result in the execution of arbitrary code with the user's privileges when GDB was run in a directory that has untrusted content. (CVE-2011-4355) With this update, GDB no longer auto-loads files from the current directory and only trusts certain system directories by default. The list of trusted directories can be viewed and modified using the 'show auto-load safe-path' and 'set auto-load safe-path' GDB commands. Refer to the GDB manual, linked to in the References, for further information. This update also fixes the following bugs : * When a struct member was at an offset greater than 256 MB, the resulting bit position within the struct overflowed and caused an invalid memory access by GDB. With this update, the code has been modified to ensure that GDB can access such positions. (BZ#795424) * When a thread list of the core file became corrupted, GDB did not print this list but displayed the 'Cannot find new threads: generic error' error message instead. With this update, GDB has been modified and it now prints the thread list of the core file as expected. (BZ#811648) * GDB did not properly handle debugging of multiple binaries with the same build ID. This update modifies GDB to use symbolic links created for particular binaries so that debugging of binaries that share a build ID now proceeds as expected. Debugging of live programs and core files is now more user-friendly. (BZ#836966) All users of gdb are advised to upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 65153
    published 2013-03-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=65153
    title CentOS 6 : gdb (CESA-2013:0522)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2013-0522.NASL
    description From Red Hat Security Advisory 2013:0522 : Updated gdb packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The GNU Debugger (GDB) allows debugging of programs written in C, C++, Java, and other languages by executing them in a controlled fashion and then printing out their data. GDB tried to auto-load certain files (such as GDB scripts, Python scripts, and a thread debugging library) from the current working directory when debugging programs. This could result in the execution of arbitrary code with the user's privileges when GDB was run in a directory that has untrusted content. (CVE-2011-4355) With this update, GDB no longer auto-loads files from the current directory and only trusts certain system directories by default. The list of trusted directories can be viewed and modified using the 'show auto-load safe-path' and 'set auto-load safe-path' GDB commands. Refer to the GDB manual, linked to in the References, for further information. This update also fixes the following bugs : * When a struct member was at an offset greater than 256 MB, the resulting bit position within the struct overflowed and caused an invalid memory access by GDB. With this update, the code has been modified to ensure that GDB can access such positions. (BZ#795424) * When a thread list of the core file became corrupted, GDB did not print this list but displayed the 'Cannot find new threads: generic error' error message instead. With this update, GDB has been modified and it now prints the thread list of the core file as expected. (BZ#811648) * GDB did not properly handle debugging of multiple binaries with the same build ID. This update modifies GDB to use symbolic links created for particular binaries so that debugging of binaries that share a build ID now proceeds as expected. Debugging of live programs and core files is now more user-friendly. (BZ#836966) All users of gdb are advised to upgrade to these updated packages, which contain backported patches to correct these issues.
    last seen 2019-02-21
    modified 2019-01-02
    plugin id 68758
    published 2013-07-12
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=68758
    title Oracle Linux 6 : gdb (ELSA-2013-0522)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2012-6635.NASL
    description Update 'set auto-load' patchset and the --with-auto-load-safe-path setting. Security fix for loading untrusted inferiors, see 'set auto-load'. Security fix for loading untrusted inferiors, see 'set auto-load'. Workaround crashes from stale frame_info pointer (BZ 804256). Security fix for loading untrusted inferiors, see 'set auto-load' (BZ 756117). Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 58999
    published 2012-05-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=58999
    title Fedora 17 : gdb-7.4.50.20120120-42.fc17 (2012-6635)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2013-159.NASL
    description GDB tried to auto-load certain files (such as GDB scripts, Python scripts, and a thread debugging library) from the current working directory when debugging programs. This could result in the execution of arbitrary code with the user's privileges when GDB was run in a directory that has untrusted content. (CVE-2011-4355) With this update, GDB no longer auto-loads files from the current directory and only trusts certain system directories by default. The list of trusted directories can be viewed and modified using the 'show auto-load safe-path' and 'set auto-load safe-path' GDB commands. Refer to the GDB manual, linked to in the References, for further information.
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 69718
    published 2013-09-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69718
    title Amazon Linux AMI : gdb (ALAS-2013-159)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2012-6614.NASL
    description Update 'set auto-load' patchset and the --with-auto-load-safe-path setting. Security fix for loading untrusted inferiors, see 'set auto-load'. Security fix for loading untrusted inferiors, see 'set auto-load'. Workaround crashes from stale frame_info pointer (BZ 804256). Security fix for loading untrusted inferiors, see 'set auto-load' (BZ 756117). Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-28
    plugin id 61585
    published 2012-08-20
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61585
    title Fedora 16 : gdb-7.3.50.20110722-16.fc16 (2012-6614)
redhat via4
advisories
bugzilla
id 836966
title Backport gdb fix to handle identical binaries via additional build-id symlinks
oval
AND
  • OR
    • comment Red Hat Enterprise Linux 6 Client is installed
      oval oval:com.redhat.rhba:tst:20111656001
    • comment Red Hat Enterprise Linux 6 Server is installed
      oval oval:com.redhat.rhba:tst:20111656002
    • comment Red Hat Enterprise Linux 6 Workstation is installed
      oval oval:com.redhat.rhba:tst:20111656003
    • comment Red Hat Enterprise Linux 6 ComputeNode is installed
      oval oval:com.redhat.rhba:tst:20111656004
  • OR
    • AND
      • comment gdb is earlier than 0:7.2-60.el6
        oval oval:com.redhat.rhsa:tst:20130522005
      • comment gdb is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20130522006
    • AND
      • comment gdb-gdbserver is earlier than 0:7.2-60.el6
        oval oval:com.redhat.rhsa:tst:20130522007
      • comment gdb-gdbserver is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20130522008
rhsa
id RHSA-2013:0522
released 2013-02-21
severity Moderate
title RHSA-2013:0522: gdb security and bug fix update (Moderate)
rpms
  • gdb-0:7.2-60.el6
  • gdb-gdbserver-0:7.2-60.el6
refmap via4
confirm http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/gdb/NEWS?content-type=text/x-cvsweb-markup&cvsroot=src
mlist
  • [gdb-patches] 20110429 Re: [RFA] Add $pdir as entry for libthread-db-search-path.
  • [gdb-patches] 20110506 Re: [RFA] Add $pdir as entry for libthread-db-search-path.
sectrack 1028191
Last major update 06-03-2013 - 00:00
Published 05-03-2013 - 16:38
Back to Top