Menu

Star on GitHub · 3.2k

CVE-2005-1705

7.2 · HIGH

gdb before 6.3 searches the current working directory to load the .gdbinit configuration file, which allows local users to execute arbitrary commands as the user running gdb.

Published May 24, 2005gnuEPSS 0.44%

Overview

CVE-2005-1705 is a high-severity vulnerability affecting gnu gdb. It was published on May 24, 2005 and has a CVSS 2.0 base score of 7.2 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

gdb before 6.3 searches the current working directory to load the .gdbinit configuration file, which allows local users to execute arbitrary commands as the user running gdb.

Remediation

Check the references section for vendor advisories and patches from gnu. Update gdb to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
gnugdb0Affected

Frequently asked questions

What is CVE-2005-1705?

CVE-2005-1705 is a high-severity vulnerability affecting gnu gdb. It was published on May 24, 2005 and has a CVSS 2.0 base score of 7.2 (HIGH).

How severe is CVE-2005-1705?

This vulnerability has a CVSS 2.0 base score of 7.2, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-1705?

Check the references section for vendor advisories and patches from gnu. Update gdb to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-1705?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-1705 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2005

View all