GNU binutils up to 2.31 BFD Library libbfd.c bfd_getl32 memory corruption

Summaryinfo

A vulnerability, which was classified as critical, has been found in GNU binutils up to 2.31. The affected element is the function bfd_getl32 of the file libbfd.c of the component BFD Library. This manipulation causes memory corruption. This vulnerability is registered as CVE-2018-17360. The attack needs to be launched locally. No exploit is available.

Detailsinfo

A vulnerability was found in GNU binutils up to 2.31 (Programming Tool Software). It has been declared as critical. Affected by this vulnerability is the function bfd_getl32 of the file libbfd.c of the component BFD Library. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. a heap-based buffer over-read in bfd_getl32 in libbfd.c allows an attacker to cause a denial of service through a crafted PE file. This vulnerability can be triggered by the executable objdump.

The bug was discovered 09/20/2018. The weakness was published 09/23/2018 (Website). The advisory is shared at sourceware.org. This vulnerability is known as CVE-2018-17360 since 09/23/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Similar entries are available at VDB-124404 and VDB-124403. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Tool Software

Vendor

• GNU

Name

• binutils

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31

License

• open-source

Website

• Vendor: https://www.gnu.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion