What is the severity of CVE-2017-9778?

CVE-2017-9778 is considered a high severity vulnerability due to its potential to cause memory exhaustion in the GNU Debugger.

How do I fix CVE-2017-9778?

To fix CVE-2017-9778, upgrade to a version of GNU Debugger newer than 8.0 where the vulnerability is addressed.

What software is affected by CVE-2017-9778?

CVE-2017-9778 affects GNU Debugger versions 8.0 and earlier.

How does CVE-2017-9778 affect GDB functionality?

CVE-2017-9778 can impede GDB's functionality by causing excessive memory allocation when handling malformed ELF binaries or core files.

What steps should I take if I can't upgrade GDB to patch CVE-2017-9778?

If upgrading is not possible, consider limiting the input to GDB to avoid using malformed ELF binaries or core files that trigger this vulnerability.

Vulnerability/
CVE-2017-9778

medium

5.5

CWE

20 770

21/6/2017

5/8/2024

CVE-2017-9778: Input Validation

First published: Wed Jun 21 2017(Updated: )

GNU Debugger (GDB) 8.0 and earlier fails to detect a negative length field in a DWARF section. A malformed section in an ELF binary or a core file can cause GDB to repeatedly allocate memory until a process limit is reached. This can, for example, impede efforts to analyze malware with GDB.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GNU gdb	<=8.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-9778?
CVE-2017-9778 is considered a high severity vulnerability due to its potential to cause memory exhaustion in the GNU Debugger.
How do I fix CVE-2017-9778?
To fix CVE-2017-9778, upgrade to a version of GNU Debugger newer than 8.0 where the vulnerability is addressed.
What software is affected by CVE-2017-9778?
CVE-2017-9778 affects GNU Debugger versions 8.0 and earlier.
How does CVE-2017-9778 affect GDB functionality?
CVE-2017-9778 can impede GDB's functionality by causing excessive memory allocation when handling malformed ELF binaries or core files.
What steps should I take if I can't upgrade GDB to patch CVE-2017-9778?
If upgrading is not possible, consider limiting the input to GDB to avoid using malformed ELF binaries or core files that trigger this vulnerability.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/weakness
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/description
agent/source
vendor/gnu
canonical/gnu gdb
version/gnu gdb/8.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-9778?
CVE-2017-9778 is considered a high severity vulnerability due to its potential to cause memory exhaustion in the GNU Debugger.
How do I fix CVE-2017-9778?
To fix CVE-2017-9778, upgrade to a version of GNU Debugger newer than 8.0 where the vulnerability is addressed.
What software is affected by CVE-2017-9778?
CVE-2017-9778 affects GNU Debugger versions 8.0 and earlier.
How does CVE-2017-9778 affect GDB functionality?
CVE-2017-9778 can impede GDB's functionality by causing excessive memory allocation when handling malformed ELF binaries or core files.
What steps should I take if I can't upgrade GDB to patch CVE-2017-9778?
If upgrading is not possible, consider limiting the input to GDB to avoid using malformed ELF binaries or core files that trigger this vulnerability.