Bug 1632914 (CVE-2018-17359) - CVE-2018-17359 binutils: invalid memory access in bfd_zalloc in opncls.c
Summary: CVE-2018-17359 binutils: invalid memory access in bfd_zalloc in opncls.c
Keywords:
Status: CLOSED DUPLICATE of bug 1632908
Alias: CVE-2018-17359
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1632909 1632910 Engineering1632911 Engineering1632912 1632913 1632915 1632916 Engineering1632917 Engineering1632918 1632919
Blocks: Embargoed1632928
TreeView+ depends on / blocked
 
Reported: 2018-09-25 20:09 UTC by Laura Pardo
Modified: 2021-02-16 23:00 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:40:15 UTC

Attachments (Terms of Use)

Description Laura Pardo 2018-09-25 20:09:43 UTC 
An issue was discovered in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.31. An invalid memory access exists in bfd_zalloc in opncls.c. Attackers could leverage this vulnerability to cause a denial of service (application crash) via a crafted ELF file.


References:
https://sourceware.org/bugzilla/show_bug.cgi?id=23686

Upstream Patch:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=30838132997e6a3cfe3ec11c58b32b22f6f6b102
Comment 1 Laura Pardo 2018-09-25 20:11:00 UTC 
Created binutils tracking bugs for this issue:

Affects: fedora-all [bug 1632916]


Created mingw-binutils tracking bugs for this issue:

Affects: epel-all [bug 1632915]
Affects: fedora-all [bug 1632919]
Comment 3 Stefan Cornelius 2020-03-27 18:40:15 UTC 

*** This bug has been marked as a duplicate of bug 1632908 ***
Comment 4 Doran Moppert 2020-06-17 04:14:40 UTC 
Statement:

This flaw was found to be a duplicate of $DUP. Please see https://access.redhat.com/security/cve/$DUP for information about affected products and security errata.
Note You need to log in before you can comment on or make changes to this bug.