CVE-2017-17123 : Security Advisory and Response

A crafted COFF based file can cause a denial of service (NULL pointer dereference and application crash) through the coff_slurp_reloc_table function in coffcode.h within the Binary File Descriptor (BFD) library (also known as libbfd), as found in GNU Binutils 2.29.1.

Understanding CVE-2017-17123

This CVE entry describes a vulnerability in the Binary File Descriptor (BFD) library in GNU Binutils 2.29.1 that can lead to a denial of service attack.

What is CVE-2017-17123?

The vulnerability in the coff_slurp_reloc_table function in the BFD library allows remote attackers to trigger a denial of service by exploiting a crafted COFF based file.

The Impact of CVE-2017-17123

The vulnerability can result in a NULL pointer dereference and application crash, potentially disrupting the affected system's functionality.

Technical Details of CVE-2017-17123

This section provides more in-depth technical information about the CVE.

Vulnerability Description

The coff_slurp_reloc_table function in coffcode.h within the BFD library in GNU Binutils 2.29.1 is susceptible to exploitation, leading to a denial of service condition.

Affected Systems and Versions

Product: Not applicable
Vendor: Not applicable
Versions affected: Not applicable

Exploitation Mechanism

The vulnerability can be exploited by using a specially crafted COFF based file to trigger the denial of service condition.

Mitigation and Prevention

Protecting systems from CVE-2017-17123 requires specific actions to mitigate the risk.

Immediate Steps to Take

Apply vendor patches or updates promptly to address the vulnerability.
Implement network security measures to prevent unauthorized access to vulnerable systems.
Monitor system logs for any suspicious activities that could indicate exploitation attempts.

Long-Term Security Practices

Regularly update software and libraries to ensure the latest security patches are in place.
Conduct security assessments and penetration testing to identify and address vulnerabilities proactively.

Patching and Updates

Check for patches or updates provided by the software vendor to fix the vulnerability.
Follow best practices for patch management to ensure timely application of security updates.