CVE-2020-35496: Null Pointer Dereference
GNU Binutils before 2.34 has a NULL pointer dereference in bfdpefscanstartaddress function in bfd/pef.c due to not checking return value of bfdmalloc. This bug allows attackers to cause a denial of service.
Reference: https://sourceware.org/bugzilla/showbug.cgi?id=25308
Other sources
GNU Binutils is vulnerable to a denial of service, caused by NULL pointer dereference in the bfdpefscanstartaddress() of bfd/pef.c. in the Binary File Descriptor (BFD) library. By persuading a victim to open a specially-crafted file with corrupt dwarf1 debug information, a remote attacker could cause a denial of service.
— IBM
There's a flaw in bfdpefscanstartaddress() of bfd/pef.c in binutils which could allow an attacker who is able to submit a crafted file to be processed by objdump to cause a NULL pointer dereference. The greatest threat of this flaw is to application availability. This flaw affects binutils versions prior to 2.34.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2020-35496?
CVE-2020-35496 is a vulnerability in bfd_pef_scan_start_address() of bfd/pef.c in binutils, which could allow a crafted file processed by objdump to cause a NULL pointer dereference.
What is the severity of CVE-2020-35496?
The severity of CVE-2020-35496 is medium, with a severity value of 5.5.
Which software is affected by CVE-2020-35496?
The software affected by CVE-2020-35496 includes the binutils package version up to exclusive 2.34, GNU Binutils version up to exclusive 2.34, Fedora 32, Netapp Cloud Backup, NetApp ONTAP Select Deploy administration utility, Netapp Solidfire, Enterprise Sds & Hci Storage Node, Netapp Solidfire & Hci Management Node, Broadcom Brocade Fabric Operating System Firmware, and Netapp Hci Compute Node Firmware.
How can I fix the CVE-2020-35496 vulnerability?
To fix the CVE-2020-35496 vulnerability, you should update binutils to version 2.34 or later.
Where can I find more information about CVE-2020-35496?
You can find more information about CVE-2020-35496 at the following references: [1] [2] [3].