Gdb vulnerabilitiesRanked by how likely they are to be used.

Product75 versions
The short answer

Gdb is made by Gnu. We track 9 published vulnerabilities in it, across 75 versions. None of them is on the list of flaws known to be exploited today. If you run Gdb, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Gdb vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Gdb's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Gdb flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 3.2%

    Buffer overflow in the (1) DWARF (dwarfread.c) and (2) DWARF2 (dwarf2read.c) debugging code in GNU Debugger (GDB) 6.5 allows user-assisted attackers, or restricted users, to execute arbitrary code via a crafted file...

    CVSS5.1Published31 Aug 2006
  2. 2.6%

    GNU gdb All versions is affected by: Buffer Overflow - Out of bound memory access.

    CVSS7.8Published24 Jul 2019
  3. 1.1%

    GNU Debugger (GDB) 8.0 and earlier fails to detect a negative length field in a DWARF section.

    CVSS5.5Published21 Jun 2017
  4. 0.6%

    Integer overflow in the Binary File Descriptor (BFD) library for gdb before 6.3, binutils, elfutils, and possibly other packages, allows user-assisted attackers to execute arbitrary code via a crafted object file...

    CVSS4.6Published24 May 2005
  5. 0.4%

    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.

    CVSS7.2Published24 May 2005
  6. 0.4%

    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...

    CVSS6.9Published5 Mar 2013
  7. 0.3%

    GNU gdb (GDB) 13.0.50.20220805-git was discovered to contain a stack overflow via the function ada_decode at /gdb/ada-lang.c.

    CVSS5.5Published25 Jul 2023
  8. 0.2%

    GNU gdb (GDB) 13.0.50.20220805-git was discovered to contain a heap use after free via the function add_pe_exported_sym() at /gdb/coff-pe-read.c.

    CVSS5.5Published25 Jul 2023
  9. 0.2%

    GNU gdb (GDB) 13.0.50.20220805-git was discovered to contain a heap buffer overflow via the function pe_as16() at /gdb/coff-pe-read.c.

    CVSS5.5Published25 Jul 2023
EdgeProtect

Running Gdb? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 9 published vulnerabilities listed under the name Gdb, across 75 versions.

None of Gdb's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Gdb. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.