{"id":"CVE-2017-9750","aliases":["CLSA-2021-1635459139","DEBIAN-CVE-2017-9750","EUVD-2017-18680","GHSA-9wwg-6rwx-49mw","MGASA-2019-0169","SUSE-SU-2017:3170-1","SUSE-SU-2018:3207-1","SUSE-SU-2018:3207-2","UBUNTU-CVE-2017-9750","USN-4336-2","USN-4336-3","openSUSE-SU-2024:10651-1"],"status":"published","title":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which...","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","severity":{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.08075,"percentile":0.94839,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-119"],"published":"2017-06-19T04:00:00Z","modified":"2026-10-24T10:31:04Z","exploits":[{"source":"exploitdb","id":"EDB-42198","title":"GNU binutils - 'rx_decode_opcode' Buffer Overflow","type":"dos","platform":"linux","date":"2017-06-19","verified":true,"url":"https://www.exploit-db.com/exploits/42198"}],"fixes":[{"ecosystem":"Debian:12","package":"binutils","fixed_in":["2.29-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"binutils","fixed_in":["2.29-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"binutils","fixed_in":["2.29-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:14.04:LTS","package":"binutils","fixed_in":["2.24-5ubuntu14.2+esm2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"binutils","fixed_in":["2.26.1-1ubuntu1~16.04.8+esm1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-aarch64-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-alpha-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-arm-linux-gnueabi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-arm-linux-gnueabihf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-hppa-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-hppa64-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-m68k-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-mips-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-mips64-linux-gnuabi64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-mips64el-linux-gnuabi64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-mipsel-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-multiarch","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-multiarch-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-powerpc-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-powerpc-linux-gnuspe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-powerpc64-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-powerpc64le-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-s390x-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-sh4-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"binutils-sparc64-linux-gnu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.10"}]}],"bundled":147},{"source":"osv","ecosystem":"Debian:12","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29-1"}]}]},{"source":"osv","ecosystem":"Mageia:6","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.32-1.1.mga6"}]}],"bundled":105},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"cross-ppc-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"cross-spu-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"cross-ppc-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"cross-spu-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.1-9.20.2"}]}],"bundled":57},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 7","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"cross-ppc-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"cross-spu-binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12-LTSS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-LTSS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 4","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-9.26.1"}]}],"bundled":52},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.24-5ubuntu14.2+esm2"}]}],"versions":["2.23.52.20130913-0ubuntu1","2.23.90.20131017-1ubuntu1","2.23.90.20131116-1ubuntu1","2.23.91.20131123-1ubuntu1","2.24-1ubuntu1","2.24-1ubuntu2","2.24-2ubuntu1","2.24-2ubuntu2","2.24-2ubuntu3","2.24-4ubuntu1","2.24-5ubuntu1","2.24-5ubuntu2","2.24-5ubuntu3","2.24-5ubuntu3.1","2.24-5ubuntu13","2.24-5ubuntu14","2.24-5ubuntu14.1","2.24-5ubuntu14.2","2.24-5ubuntu14.2+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.8+esm1"}]}],"versions":["2.25.1-6ubuntu1","2.25.51.20151022-0ubuntu2","2.25.51.20151022-0ubuntu3","2.25.51.20151027-0ubuntu1","2.25.51.20151028-0ubuntu1","2.25.51.20151106-0ubuntu1","2.25.51.20151113-1ubuntu1","2.25.51.20151113-2ubuntu1","2.25.90.20151125-1ubuntu1","2.25.90.20151125-2ubuntu1","2.25.90.20151211-0ubuntu1","2.25.90.20151211-0ubuntu2","2.25.90.20160101-1ubuntu1","2.25.90.20160101-1ubuntu2","2.26-2ubuntu1","2.26-3ubuntu1","2.26-4ubuntu1","2.26-5ubuntu1","2.26-6ubuntu1","2.26-7ubuntu2","2.26-8ubuntu1","2.26-8ubuntu2","2.26-8ubuntu2.1","2.26.1-1ubuntu1~16.04","2.26.1-1ubuntu1~16.04.1","2.26.1-1ubuntu1~16.04.3","2.26.1-1ubuntu1~16.04.4","2.26.1-1ubuntu1~16.04.5","2.26.1-1ubuntu1~16.04.6","2.26.1-1ubuntu1~16.04.7","2.26.1-1ubuntu1~16.04.8"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.26.1-1ubuntu1~16.04.8+esm1"}]}],"versions":["2.25.1-6ubuntu1","2.25.51.20151022-0ubuntu2","2.25.51.20151022-0ubuntu3","2.25.51.20151027-0ubuntu1","2.25.51.20151028-0ubuntu1","2.25.51.20151106-0ubuntu1","2.25.51.20151113-1ubuntu1","2.25.51.20151113-2ubuntu1","2.25.90.20151125-1ubuntu1","2.25.90.20151125-2ubuntu1","2.25.90.20151211-0ubuntu1","2.25.90.20151211-0ubuntu2","2.25.90.20160101-1ubuntu1","2.25.90.20160101-1ubuntu2","2.26-2ubuntu1","2.26-3ubuntu1","2.26-4ubuntu1","2.26-5ubuntu1","2.26-6ubuntu1","2.26-7ubuntu2","2.26-8ubuntu1","2.26-8ubuntu2","2.26-8ubuntu2.1","2.26.1-1ubuntu1~16.04","2.26.1-1ubuntu1~16.04.1","2.26.1-1ubuntu1~16.04.3","2.26.1-1ubuntu1~16.04.4","2.26.1-1ubuntu1~16.04.5","2.26.1-1ubuntu1~16.04.6","2.26.1-1ubuntu1~16.04.7","2.26.1-1ubuntu1~16.04.8"],"bundled":147},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.24-5ubuntu14.2+esm2"}]}],"versions":["2.23.52.20130913-0ubuntu1","2.23.90.20131017-1ubuntu1","2.23.90.20131116-1ubuntu1","2.23.91.20131123-1ubuntu1","2.24-1ubuntu1","2.24-1ubuntu2","2.24-2ubuntu1","2.24-2ubuntu2","2.24-2ubuntu3","2.24-4ubuntu1","2.24-5ubuntu1","2.24-5ubuntu2","2.24-5ubuntu3","2.24-5ubuntu3.1","2.24-5ubuntu13","2.24-5ubuntu14","2.24-5ubuntu14.1","2.24-5ubuntu14.2","2.24-5ubuntu14.2+esm1"],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.37-1.3"}]}],"bundled":106}],"products":[{"vendor":"gnu","product":"binutils"}],"references":[{"url":"http://www.securityfocus.com/bid/99118","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://security.gentoo.org/glsa/201801-01","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","advisory"]},{"url":"https://www.exploit-db.com/exploits/42198/","tags":["exploit","x_refsource_EXPLOIT-DB","x_transferred","web"]},{"url":"https://sourceware.org/bugzilla/show_bug.cgi?id=21587","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-9750"},{"url":"https://www.exploit-db.com/exploits/42198"},{"url":"https://github.com/advisories/GHSA-9wwg-6rwx-49mw"},{"url":"https://errata.cloudlinux.com/ubuntu16_04/CLSA-2021-1635459139","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-9750","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2019-0169.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=18987","tags":["report"]},{"url":"https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_32","tags":["web"]},{"url":"https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gas/NEWS;hb=refs/tags/binutils-2_32","tags":["web"]},{"url":"https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=ld/NEWS;hb=refs/tags/binutils-2_32","tags":["web"]},{"url":"https://lwn.net/Alerts/694764/","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/03/16/8","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/04/10/16","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/05/18/7","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/09/26/6","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/09/30/1","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/09/30/2","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/09/30/3","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/3","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/6","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/4","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/5","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/8","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/04/7","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/27/4","tags":["web"]},{"url":"https://openwall.com/lists/oss-security/2017/10/27/3","tags":["web"]},{"url":"https://lists.opensuse.org/opensuse-updates/2017-12/msg00008.html","tags":["web"]},{"url":"https://lists.suse.com/pipermail/sle-security-updates/2018-October/004678.html","tags":["web"]},{"url":"https://lists.suse.com/pipermail/sle-security-updates/2018-October/004683.html","tags":["web"]},{"url":"https://lists.opensuse.org/opensuse-updates/2018-10/msg00104.html","tags":["web"]},{"url":"https://lists.opensuse.org/opensuse-updates/2018-10/msg00133.html","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/37N6SA4WSBTFWAMPQXHSO7JRJQ6EIIO5/","tags":["web"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1645958","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20173170-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1003846","tags":["report"]},{"url":"https://bugzilla.suse.com/1025282","tags":["report"]},{"url":"https://bugzilla.suse.com/1029907","tags":["report"]},{"url":"https://bugzilla.suse.com/1029908","tags":["report"]},{"url":"https://bugzilla.suse.com/1029909","tags":["report"]},{"url":"https://bugzilla.suse.com/1029995","tags":["report"]},{"url":"https://bugzilla.suse.com/1030296","tags":["report"]},{"url":"https://bugzilla.suse.com/1030297","tags":["report"]},{"url":"https://bugzilla.suse.com/1030298","tags":["report"]},{"url":"https://bugzilla.suse.com/1030583","tags":["report"]},{"url":"https://bugzilla.suse.com/1030584","tags":["report"]},{"url":"https://bugzilla.suse.com/1030585","tags":["report"]},{"url":"https://bugzilla.suse.com/1030588","tags":["report"]},{"url":"https://bugzilla.suse.com/1030589","tags":["report"]},{"url":"https://bugzilla.suse.com/1031590","tags":["report"]},{"url":"https://bugzilla.suse.com/1031593","tags":["report"]},{"url":"https://bugzilla.suse.com/1031595","tags":["report"]},{"url":"https://bugzilla.suse.com/1031638","tags":["report"]},{"url":"https://bugzilla.suse.com/1031644","tags":["report"]},{"url":"https://bugzilla.suse.com/1031656","tags":["report"]},{"url":"https://bugzilla.suse.com/1033122","tags":["report"]},{"url":"https://bugzilla.suse.com/1037052","tags":["report"]},{"url":"https://bugzilla.suse.com/1037057","tags":["report"]},{"url":"https://bugzilla.suse.com/1037061","tags":["report"]},{"url":"https://bugzilla.suse.com/1037062","tags":["report"]},{"url":"https://bugzilla.suse.com/1037066","tags":["report"]},{"url":"https://bugzilla.suse.com/1037070","tags":["report"]},{"url":"https://bugzilla.suse.com/1037072","tags":["report"]},{"url":"https://bugzilla.suse.com/1037273","tags":["report"]},{"url":"https://bugzilla.suse.com/1038874","tags":["report"]},{"url":"https://bugzilla.suse.com/1038875","tags":["report"]},{"url":"https://bugzilla.suse.com/1038876","tags":["report"]},{"url":"https://bugzilla.suse.com/1038877","tags":["report"]},{"url":"https://bugzilla.suse.com/1038878","tags":["report"]},{"url":"https://bugzilla.suse.com/1038880","tags":["report"]},{"url":"https://bugzilla.suse.com/1038881","tags":["report"]},{"url":"https://bugzilla.suse.com/1044891","tags":["report"]},{"url":"https://bugzilla.suse.com/1044897","tags":["report"]},{"url":"https://bugzilla.suse.com/1044901","tags":["report"]},{"url":"https://bugzilla.suse.com/1044909","tags":["report"]},{"url":"https://bugzilla.suse.com/1044925","tags":["report"]},{"url":"https://bugzilla.suse.com/1044927","tags":["report"]},{"url":"https://bugzilla.suse.com/1046094","tags":["report"]},{"url":"https://bugzilla.suse.com/1052061","tags":["report"]},{"url":"https://bugzilla.suse.com/1052496","tags":["report"]},{"url":"https://bugzilla.suse.com/1052503","tags":["report"]},{"url":"https://bugzilla.suse.com/1052507","tags":["report"]},{"url":"https://bugzilla.suse.com/1052509","tags":["report"]},{"url":"https://bugzilla.suse.com/1052511","tags":["report"]},{"url":"https://bugzilla.suse.com/1052514","tags":["report"]},{"url":"https://bugzilla.suse.com/1052518","tags":["report"]},{"url":"https://bugzilla.suse.com/1053347","tags":["report"]},{"url":"https://bugzilla.suse.com/1056312","tags":["report"]},{"url":"https://bugzilla.suse.com/1056437","tags":["report"]},{"url":"https://bugzilla.suse.com/1057139","tags":["report"]},{"url":"https://bugzilla.suse.com/1057144","tags":["report"]},{"url":"https://bugzilla.suse.com/1057149","tags":["report"]},{"url":"https://bugzilla.suse.com/1058480","tags":["report"]},{"url":"https://bugzilla.suse.com/1059050","tags":["report"]},{"url":"https://bugzilla.suse.com/1060599","tags":["report"]},{"url":"https://bugzilla.suse.com/1060621","tags":["report"]},{"url":"https://bugzilla.suse.com/1061241","tags":["report"]},{"url":"https://bugzilla.suse.com/437293","tags":["report"]},{"url":"https://bugzilla.suse.com/445037","tags":["report"]},{"url":"https://bugzilla.suse.com/546106","tags":["report"]},{"url":"https://bugzilla.suse.com/561142","tags":["report"]},{"url":"https://bugzilla.suse.com/578249","tags":["report"]},{"url":"https://bugzilla.suse.com/590820","tags":["report"]},{"url":"https://bugzilla.suse.com/691290","tags":["report"]},{"url":"https://bugzilla.suse.com/698346","tags":["report"]},{"url":"https://bugzilla.suse.com/713504","tags":["report"]},{"url":"https://bugzilla.suse.com/776968","tags":["report"]},{"url":"https://bugzilla.suse.com/863764","tags":["report"]},{"url":"https://bugzilla.suse.com/938658","tags":["report"]},{"url":"https://bugzilla.suse.com/970239","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14745","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7614","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9955","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20183207-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1065643","tags":["report"]},{"url":"https://bugzilla.suse.com/1065689","tags":["report"]},{"url":"https://bugzilla.suse.com/1065693","tags":["report"]},{"url":"https://bugzilla.suse.com/1068640","tags":["report"]},{"url":"https://bugzilla.suse.com/1068643","tags":["report"]},{"url":"https://bugzilla.suse.com/1068887","tags":["report"]},{"url":"https://bugzilla.suse.com/1068888","tags":["report"]},{"url":"https://bugzilla.suse.com/1068950","tags":["report"]},{"url":"https://bugzilla.suse.com/1069176","tags":["report"]},{"url":"https://bugzilla.suse.com/1069202","tags":["report"]},{"url":"https://bugzilla.suse.com/1074741","tags":["report"]},{"url":"https://bugzilla.suse.com/1077745","tags":["report"]},{"url":"https://bugzilla.suse.com/1079103","tags":["report"]},{"url":"https://bugzilla.suse.com/1079741","tags":["report"]},{"url":"https://bugzilla.suse.com/1080556","tags":["report"]},{"url":"https://bugzilla.suse.com/1081527","tags":["report"]},{"url":"https://bugzilla.suse.com/1083528","tags":["report"]},{"url":"https://bugzilla.suse.com/1083532","tags":["report"]},{"url":"https://bugzilla.suse.com/1085784","tags":["report"]},{"url":"https://bugzilla.suse.com/1086608","tags":["report"]},{"url":"https://bugzilla.suse.com/1086784","tags":["report"]},{"url":"https://bugzilla.suse.com/1086786","tags":["report"]},{"url":"https://bugzilla.suse.com/1086788","tags":["report"]},{"url":"https://bugzilla.suse.com/1090997","tags":["report"]},{"url":"https://bugzilla.suse.com/1091015","tags":["report"]},{"url":"https://bugzilla.suse.com/1091365","tags":["report"]},{"url":"https://bugzilla.suse.com/1091368","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-6323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-6543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-6759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-6872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8945","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20183207-2/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2017-9750","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-4336-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-4336-3","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-9750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-2226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4492","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-4493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-6131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6966","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8397","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8398","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-8421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9751","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-9954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12451","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12452","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12453","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12454","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-12967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-13710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15939","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-6323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-6543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-6759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7642","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-7643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-8945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-9138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10534","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-10535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12641","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-12934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-13033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-17358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-17359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-17360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-17794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-17985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18484","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18605","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18606","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-18701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-19931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-19932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-1000876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-9077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-12972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-14250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-14444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-17450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-17451","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-1010180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-12972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16592","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-35448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-35493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-35496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-35507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3487","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-9750","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:00:00Z","modified":"2024-08-05T17:18:01.433Z","updated_at":"2026-11-02T14:33:13.96587Z"}],"euvd":[{"id":"EUVD-2017-18680","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:00:00Z","modified":"2024-08-05T17:18:01Z","updated_at":"2026-11-03T02:23:27.257081Z"}],"ghsa":[{"id":"GHSA-9wwg-6rwx-49mw","title":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which...","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2022-05-14T03:52:21Z","modified":"2025-04-20T03:40:22Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T15:01:48.455381Z"}],"nvd":[{"id":"CVE-2017-9750","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:29:00.483Z","modified":"2026-06-17T01:28:49.89Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T14:03:50.782497Z"}],"osv":[{"id":"CVE-2017-9750","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:29:00.483Z","modified":"2026-10-24T10:31:04.102500583Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:07.192756Z"},{"id":"DEBIAN-CVE-2017-9750","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:29:00.483Z","modified":"2026-09-01T20:03:52.253253879Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:29.698576Z"},{"id":"UBUNTU-CVE-2017-9750","description":"opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during \"objdump -D\" execution.","status":"published","published":"2017-06-19T04:29:00Z","modified":"2026-04-22T11:37:59.237612Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:16.154988Z"},{"id":"CLSA-2021-1635459139","title":"Fix CVE(s): CVE-2018-6323, CVE-2017-8421, CVE-2017-15024, CVE-2017-15025, CVE-2017-15022, CVE-2017-15020, CVE-2017-15021, CVE-2017-15225, CVE-2018-18483, CVE-2017-15996, CVE-2018-18484, CVE-2017-12799, CVE-2017-16831, CVE-2017-16832, CVE-2018-1000876, CVE-2018-7208, CVE-2019-14250, CVE-2017-12967, CVE-2019-9075, CVE-2017-17080, CVE-2019-9074, CVE-2018-17794, CVE-2017-17125, CVE-2017-17124, CVE-2017-17121, CVE-2017-6969, CVE-2017-17123, CVE-2018-17358, CVE-2017-6965, CVE-2017-6966, CVE-2018-12641, CVE-2018-8945, CVE-2017-7299, CVE-2018-12699, CVE-2018-10372, CVE-2018-10373, CVE-2019-17451, CVE-2019-17450, CVE-2018-18701, CVE-2018-18700, CVE-2017-7210, CVE-2018-20623, CVE-2017-15938, CVE-2017-15939, CVE-2017-9039, CVE-2017-9038, CVE-2017-14940, CVE-2018-17985, CVE-2018-12700, CVE-2017-9742, CVE-2017-9745, CVE-2017-9744, CVE-2017-9747, CVE-2017-7209, CVE-2017-9749, CVE-2017-9748, CVE-2018-9138, CVE-2017-16828, CVE-2017-16827, CVE-2017-16826, CVE-2017-7614, CVE-2018-6759, CVE-2016-4491, CVE-2017-9044, CVE-2017-9746, CVE-2017-9042, CVE-2017-9040, CVE-2017-9041, CVE-2017-9752, CVE-2017-9753, CVE-2017-9750, CVE-2017-9751, CVE-2017-9756, CVE-2016-4493, CVE-2017-9754, CVE-2017-9755, CVE-2016-4492, CVE-2018-19932, CVE-2017-12458, CVE-2017-12459, CVE-2018-18606, CVE-2018-18607, CVE-2018-18605, CVE-2017-12452, CVE-2017-12453, CVE-2017-12450, CVE-2017-12451, CVE-2017-12456, CVE-2016-4490, CVE-2017-12454, CVE-2017-12455, CVE-2019-14444, CVE-2016-2226, CVE-2017-7224, CVE-2017-7225, CVE-2017-7226, CVE-2017-7227, CVE-2018-18309, CVE-2017-7223, CVE-2017-12449, CVE-2017-12448, CVE-2016-4488, CVE-2016-4489, CVE-2018-17359, CVE-2016-4487, CVE-2018-20671, CVE-2018-20002, CVE-2017-14128, CVE-2017-14129, CVE-2018-7568, CVE-2018-7569, CVE-2017-7302, CVE-2017-7301, CVE-2017-7300, CVE-2018-12934, CVE-2017-8394, CVE-2018-7643, CVE-2018-7642, CVE-2018-17360, CVE-2019-12972, CVE-2018-13033, CVE-2018-19931, CVE-2018-10534, CVE-2018-10535, CVE-2019-9077, CVE-2019-9071, CVE-2019-9070, CVE-2019-9073, CVE-2017-14333, CVE-2018-12698, CVE-2017-14130, CVE-2018-12697, CVE-2018-6543, CVE-2017-9954, CVE-2017-12457, CVE-2017-14939, CVE-2017-14938, CVE-2017-14932, CVE-2017-14930, CVE-2017-8398, CVE-2017-8393, CVE-2017-8395, CVE-2017-14529, CVE-2017-8397, CVE-2017-8396, CVE-2017-13710, CVE-2016-6131","description":"\n   * SECURITY UPDATE:\n     - CVE-*.patch: backported many upstream patches to fix security issues.\n     - CVE-2016-2226, CVE-2016-4487, CVE-2016-4488, CVE-2016-4489,\n       CVE-2016-4490, CVE-2016-4492, CVE-2016-4493, CVE-2016-6131,\n       CVE-2016-4491, CVE-2017-6965, CVE-2017-6966, CVE-2017-6969,\n       CVE-2017-7209, CVE-2017-7210, CVE-2017-7223, CVE-2017-7224,\n       CVE-2017-7225, CVE-2017-7226, CVE-2017-7227, CVE-2017-7299,\n       CVE-2017-7300, CVE-2017-7301, CVE-2017-7302, CVE-2017-7614,\n       CVE-2017-8393, CVE-2017-8394, CVE-2017-8395, CVE-2017-8397,\n       CVE-2017-8396, CVE-2017-8398, CVE-2017-8421, CVE-2017-9038,\n       CVE-2017-9039, CVE-2017-9040, CVE-2017-9042, CVE-2017-9041,\n       CVE-2017-9044, CVE-2017-9742, CVE-2017-9744, CVE-2017-9752,\n       CVE-2017-9745, CVE-2017-9746, CVE-2017-9747, CVE-2017-9748,\n       CVE-2017-9749, CVE-2017-9750, CVE-2017-9751, CVE-2017-9753,\n       CVE-2017-9754, CVE-2017-9755, CVE-2017-9756, CVE-2017-9954,\n       CVE-2017-12448, CVE-2017-12449, CVE-2017-12455, CVE-2017-12457,\n       CVE-2017-12458, CVE-2017-12459, CVE-2017-12450, CVE-2017-12452,\n       CVE-2017-12453, CVE-2017-12454, CVE-2017-12456, CVE-2017-14333,\n       CVE-2017-12451, CVE-2017-12799, CVE-2017-12967, CVE-2017-13710,\n       CVE-2017-14128, CVE-2017-14129, CVE-2017-14130, CVE-2017-14529,\n       CVE-2017-14930, CVE-2017-14932, CVE-2017-14938, CVE-2017-14939,\n       CVE-2017-14940, CVE-2017-15020, CVE-2017-15021, CVE-2017-15022,\n       CVE-2017-15024, CVE-2017-15025, CVE-2017-15225, CVE-2017-15938,\n       CVE-2017-15939, CVE-2017-15996, CVE-2017-16826, CVE-2017-16827,\n       CVE-2017-16828, CVE-2017-16831, CVE-2017-16832, CVE-2017-17080,\n       CVE-2017-17121, CVE-2017-17123, CVE-2017-17124, CVE-2018-6323,\n       CVE-2018-6543, CVE-2018-6759, CVE-2018-7208, CVE-2018-7568,\n       CVE-2018-7569, CVE-2018-7642, CVE-2018-7643, CVE-2018-8945,\n       CVE-2018-13033, CVE-2018-9138, CVE-2018-12641, CVE-2018-12697,\n       CVE-2018-12698, CVE-2018-12699, CVE-2018-12700, CVE-2018-17794,\n       CVE-2018-17985, CVE-2018-18484, CVE-2018-18700, CVE-2018-18701,\n       CVE-2018-10372, CVE-2018-10373, CVE-2018-10534, CVE-2018-10535,\n       CVE-2018-12934, CVE-2018-18483, CVE-2018-17358, CVE-2018-17359,\n       CVE-2018-17360, CVE-2018-18309, CVE-2018-18605, CVE-2018-18606,\n       CVE-2018-18607, CVE-2018-19931, CVE-2018-19932, CVE-2018-20002,\n       CVE-2018-20623, CVE-2018-20671, CVE-2018-1000876, CVE-2017-17125,\n       CVE-2019-9073, CVE-2019-9074, CVE-2019-9075, CVE-2019-9077,\n       CVE-2019-9070, CVE-2019-9071, CVE-2019-12972, CVE-2019-14250,\n       CVE-2019-14444, CVE-2019-17450, CVE-2019-17451","status":"published","published":"2021-10-28T22:12:19Z","modified":"2026-06-04T10:03:55.348932283Z","updated_at":"2026-11-02T15:43:39.801198Z"},{"id":"MGASA-2019-0169","title":"Updated binutils packages fixes security vulnerabilities","description":"This update provides the latest stable binutils, currently version 2.32\nand fixes at least the following security issues:\n\nihex.c in GNU Binutils before 2.26 contains a stack buffer overflow when\nprinting bad bytes in Intel Hex objects (CVE-2014-9939)\n\nUse-after-free vulnerability in libiberty allows remote attackers to cause\na denial of service (segmentation fault and crash) via a crafted binary,\nrelated to \"btypevec.\" (CVE-2016-4487)\n\nUse-after-free vulnerability in libiberty allows remote attackers to cause\na denial of service (segmentation fault and crash) via a crafted binary,\nrelated to \"ktypevec.\" (CVE-2016-4488)\n\nInteger overflow in the gnu_special function in libiberty allows remote\nattackers to cause a denial of service (segmentation fault and crash) via\na crafted binary, related to the \"demangling of virtual tables.\"\n(CVE-2016-4489)\n\nInteger overflow in cp-demangle.c in libiberty allows remote attackers to\ncause a denial of service (segmentation fault and crash) via a crafted\nbinary, related to inconsistent use of the long and int types for lengths.\n(CVE-2016-4490)\n\nBuffer overflow in the do_type function in cplus-dem.c in libiberty allows\nremote attackers to cause a denial of service (segmentation fault and\ncrash) via a crafted binary. (CVE-2016-4492)\n\nThe demangle_template_value_parm and do_hpacc_template_literal functions\nin cplus-dem.c in libiberty allow remote attackers to cause a denial of\nservice (out-of-bounds read and crash) via a crafted binary. \n(CVE-2016-4493)\n\nThe demangler in GNU Libiberty allows remote attackers to cause a denial\nof service (infinite loop, stack overflow, and crash) via a cycle in the\nreferences of remembered mangled types. (CVE-2016-6131)\n\nreadelf in GNU Binutils 2.28 writes to illegal addresses while processing\ncorrupt input files containing symbol-difference relocations, leading to\na heap-based buffer overflow. (CVE-2017-6965)\n\nreadelf in GNU Binutils 2.28 has a use-after-free (specifically\nread-after-free) error while processing multiple, relocated sections in an\nMSP430 binary. This is caused by mishandling of an invalid symbol index,\nand mishandling of state across invocations. (CVE-2017-6966)\n\nreadelf in GNU Binutils 2.28 is vulnerable to a heap-based buffer over-read\nwhile processing corrupt RL78 binaries. The vulnerability can trigger\nprogram crashes. It may lead to an information leak as well. (CVE-2017-6969)\n\nThe dump_section_as_bytes function in readelf in GNU Binutils 2.28 accesses\na NULL pointer while reading section contents in a corrupt binary, leading\nto a program crash. (CVE-2017-7209)\n\nobjdump in GNU Binutils 2.28 is vulnerable to multiple heap-based buffer\nover-reads (of size 1 and size 8) while handling corrupt STABS enum type\nstrings in a crafted object file, leading to program crash. (CVE-2017-7210)\n\nGNU assembler in GNU Binutils 2.28 is vulnerable to a global buffer\noverflow (of size 1) while attempting to unget an EOF character from the\ninput stream, potentially leading to a program crash. (CVE-2017-7223)\n\nThe find_nearest_line function in objdump in GNU Binutils 2.28 is vulnerable\nto an invalid write (of size 1) while disassembling a corrupt binary that\ncontains an empty function name, leading to a program crash. (CVE-2017-7224)\n\nThe find_nearest_line function in addr2line in GNU Binutils 2.28 does not\nhandle the case where the main file name and the directory name are both\nempty, triggering a NULL pointer dereference and an invalid write, and\nleading to a program crash. (CVE-2017-7225)\n\nThe pe_ILF_object_p function in the Binary File Descriptor (BFD) library\n(aka libbfd), as distributed in GNU Binutils 2.28, is vulnerable to a\nheap-based buffer over-read of size 4049 because it uses the strlen\nfunction instead of strnlen, leading to program crashes in several\nutilities such as addr2line, size, and strings. It could lead to\ninformation disclosure as well. (CVE-2017-7226)\n\nGNU linker (ld) in GNU Binutils 2.28 is vulnerable to a heap-based buffer\noverflow while processing a bogus input script, leading to a program\ncrash. This relates to lack of '\\0' termination of a name field in ldlex.l.\n(CVE-2017-7227)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, has an invalid read (of size 8) because the code to\nemit relocs (bfd_elf_final_link function in bfd/elflink.c) does not check\nthe format of the input file before trying to read the ELF reloc section\nheader. The vulnerability leads to a GNU linker (ld) program crash.\n(CVE-2017-7299)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, has an aout_link_add_symbols function in bfd/aoutx.h\nthat is vulnerable to a heap-based buffer over-read (off-by-one) because\nof an incomplete check for invalid string offsets while loading symbols,\nleading to a GNU linker (ld) program crash. (CVE-2017-7300)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, has an aout_link_add_symbols function in bfd/aoutx.h\nthat has an off-by-one vulnerability because it does not carefully check\nthe string offset. The vulnerability could lead to a GNU linker (ld)\nprogram crash. (CVE-2017-7301)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, has a swap_std_reloc_out function in bfd/aoutx.h that\nis vulnerable to an invalid read (of size 4) because of missing checks\nfor relocs that could not be recognised. This vulnerability causes\nBinutils utilities like strip to crash. (CVE-2017-7302)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read (of size 4) because\nof missing a check (in the find_link function) for null headers before\nattempting to match them. This vulnerability causes Binutils utilities\nlike strip to crash. (CVE-2017-7303)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read (of size 8) because\nof missing a check (in the copy_special_section_fields function) for an\ninvalid sh_link field before attempting to follow it. This vulnerability\ncauses Binutils utilities like strip to crash. (CVE-2017-7304)\n\nelflink.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.28, has a \"member access within null\npointer\" undefined behavior issue, which might allow remote attackers to\ncause a denial of service (application crash) or possibly have unspecified\nother impact via an \"int main() {return 0;}\" program. (CVE-2017-7614)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read of size 8 because of\nmissing a check to determine whether symbols are NULL in the \n_bfd_dwarf2_find_nearest_line function. This vulnerability causes programs\nthat conduct an analysis of binary programs using the libbfd library,\nsuch as objdump, to crash. (CVE-2017-8392)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to a global buffer over-read error\nbecause of an assumption made by code that runs for objcopy and strip,\nthat SHT_REL/SHR_RELA sections are always named starting with a \n.rel/.rela prefix. This vulnerability causes programs that conduct an\nanalysis of binary programs using the libbfd library, such as objcopy\nand strip, to crash. (CVE-2017-8393)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read of size 4 due to NULL\npointer dereferencing of _bfd_elf_large_com_section. This vulnerability\ncauses programs that conduct an analysis of binary programs using the\nlibbfd library, such as objcopy, to crash. (CVE-2017-8394)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid write of size 8 because of\nmissing a malloc() return-value check to see if memory had actually been\nallocated in the _bfd_generic_get_section_contents function. This\nvulnerability causes programs that conduct an analysis of binary programs\nusing the libbfd library, such as objcopy, to crash. (CVE-2017-8395)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read of size 1 because the\nexisting reloc offset range tests didn't catch small negative offsets less\nthan the size of the reloc field. This vulnerability causes programs that\nconduct an analysis of binary programs using the libbfd library, such as\nobjdump, to crash. (CVE-2017-8396)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.28, is vulnerable to an invalid read of size 1 and an\ninvalid write of size 1 during processing of a corrupt binary containing\nreloc(s) with negative addresses. This vulnerability causes programs that\nconduct an analysis of binary programs using the libbfd library, such as\nobjdump, to crash. (CVE-2017-8397)\n\ndwarf.c in GNU Binutils 2.28 is vulnerable to an invalid read of size 1\nduring dumping of debug information from a corrupt binary. This\nvulnerability causes programs that conduct an analysis of binary programs,\nsuch as objdump and readelf, to crash. (CVE-2017-8398)\n\nThe function coff_set_alignment_hook in coffcode.h in Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.28,\nhas a memory leak vulnerability which can cause memory exhaustion in\nobjdump via a crafted PE file. Additional validation in\ndump_relocs_in_section in objdump.c can resolve this. (CVE-2017-8421)\n\nGNU Binutils 2.28 allows remote attackers to cause a denial of service\n(heap-based buffer over-read and application crash) via a crafted ELF file,\nrelated to the byte_get_little_endian function in elfcomm.c, the\nget_unwind_section_word function in readelf.c, and ARM unwind information\nthat contains invalid word offsets. (CVE-2017-9038)\n\nGNU Binutils 2.28 allows remote attackers to cause a denial of service\n(memory consumption) via a crafted ELF file with many program headers,\nrelated to the get_program_headers function in readelf.c. (CVE-2017-9039)\n\nGNU Binutils 2017-04-03 allows remote attackers to cause a denial of\nservice (NULL pointer dereference and application crash), related to the\nprocess_mips_specific function in readelf.c, via a crafted ELF file that\ntriggers a large memory-allocation attempt. (CVE-2017-9040)\n\nGNU Binutils 2.28 allows remote attackers to cause a denial of service\n(heap-based buffer over-read and application crash) via a crafted ELF file,\nrelated to MIPS GOT mishandling in the process_mips_specific function in\nreadelf.c. (CVE-2017-9041)\n\nreadelf.c in GNU Binutils 2017-04-12 has a \"cannot be represented in type\nlong\" issue, which might allow remote attackers to cause a denial of service\n(application crash) or possibly have unspecified other impact via a crafted\nELF file. (CVE-2017-9042)\n\nreadelf.c in GNU Binutils 2017-04-12 has a \"shift exponent too large for\ntype unsigned long\" issue, which might allow remote attackers to cause a\ndenial of service (application crash) or possibly have unspecified other\nimpact via a crafted ELF file. (CVE-2017-9043)\n\nThe print_symbol_for_build_attribute function in readelf.c in GNU Binutils\n2017-04-12 allows remote attackers to cause a denial of service (invalid\nread and SEGV) via a crafted ELF file. (CVE-2017-9044)\n\nThe disassemble_bytes function in objdump.c in GNU Binutils 2.28 allows\nremote attackers to cause a denial of service (buffer overflow and\napplication crash) or possibly have unspecified other impact via a crafted\nbinary file, as demonstrated by mishandling of rae insns printing for this\nfile during \"objdump -D\" execution. (CVE-2017-9746)\n\nThe ieee_archive_p function in bfd/ieee.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, might\nallow remote attackers to cause a denial of service (buffer overflow and\napplication crash) or possibly have unspecified other impact via a crafted\nbinary file, as demonstrated by mishandling of this file during\n\"objdump -D\" execution. (CVE-2017-9747)\n\nThe ieee_object_p function in bfd/ieee.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.28, might\nallow remote attackers to cause a denial of service (buffer overflow and\napplication crash) or possibly have unspecified other impact via a crafted\nbinary file, as demonstrated by mishandling of this file during\n\"objdump -D\" execution. (CVE-2017-9748)\n\nopcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain\nscale arrays, which allows remote attackers to cause a denial of service\n(buffer overflow and application crash) or possibly have unspecified other\nimpact via a crafted binary file, as demonstrated by mishandling of this\nfile during \"objdump -D\" execution. (CVE-2017-9750)\n\nopcodes/i386-dis.c in GNU Binutils 2.28 does not consider the number of\nregisters for bnd mode, which allows remote attackers to cause a denial\nof service (buffer overflow and application crash) or possibly have\nunspecified other impact via a crafted binary file, as demonstrated by\nmishandling of this file during \"objdump -D\" execution. (CVE-2017-9755)\n\nThe aarch64_ext_ldst_reglist function in opcodes/aarch64-dis.c in GNU\nBinutils 2.28 allows remote attackers to cause a denial of service\n(buffer overflow and application crash) or possibly have unspecified\nother impact via a crafted binary file, as demonstrated by mishandling\nof this file during \"objdump -D\" execution. (CVE-2017-9756)\n\nThe getvalue function in tekhex.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.28, allows remote\nattackers to cause a denial of service (stack-based buffer over-read and\napplication crash) via a crafted tekhex file, as demonstrated by\nmishandling within the nm program. (CVE-2017-9954)\n\nThe get_build_id function in opncls.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.28, allows remote\nattackers to cause a denial of service (heap-based buffer over-read and\napplication crash) via a crafted file in which a certain size field is\nlarger than a corresponding data field, as demonstrated by mishandling\nwithin the objdump program. (CVE-2017-9955)\n\nThe bfd_cache_close function in bfd/cache.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier,\nallows remote attackers to cause a heap use after free and possibly achieve\ncode execution via a crafted nested archive file. This issue occurs because\nincorrect functions are called during an attempt to release memory. The\nissue can be addressed by better input validation in the\nbfd_generic_archive_p function in bfd/archive.c. (CVE-2017-12448)\n\nThe _bfd_vms_save_sized_string function in vms-misc.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29\nand earlier, allows remote attackers to cause an out of bounds heap read\nvia a crafted vms file. (CVE-2017-12449)\n\nThe alpha_vms_object_p function in bfd/vms-alpha.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29\nand earlier, allows remote attackers to cause an out of bounds heap write\nand possibly achieve code execution via a crafted vms alpha file.\n(CVE-2017-12450)\n\nThe _bfd_xcoff_read_ar_hdr function in bfd/coff-rs6000.c and\nbfd/coff64-rs6000.c in the Binary File Descriptor (BFD) library (aka\nlibbfd), as distributed in GNU Binutils 2.29 and earlier, allows remote\nattackers to cause an out of bounds stack read via a crafted COFF image\nfile. (CVE-2017-12451)\n\nThe bfd_mach_o_i386_canonicalize_one_reloc function in bfd/mach-o-i386.c\nin the Binary File Descriptor (BFD) library (aka libbfd), as distributed\nin GNU Binutils 2.29 and earlier, allows remote attackers to cause an out\nof bounds heap read via a crafted mach-o file. (CVE-2017-12452)\n\nThe _bfd_vms_slurp_eeom function in libbfd.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.29 and earlier,\nallows remote attackers to cause an out of bounds heap read via a crafted\nvms alpha file. (CVE-2017-12453)\n\nThe _bfd_vms_slurp_egsd function in bfd/vms-alpha.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29\nand earlier, allows remote attackers to cause an arbitrary memory read via\na crafted vms alpha file. (CVE-2017-12454)\n\nThe evax_bfd_print_emh function in vms-alpha.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29\nand earlier, allows remote attackers to cause an out of bounds heap read\nvia a crafted vms alpha file. (CVE-2017-12455)\n\nThe read_symbol_stabs_debugging_info function in rddbg.c in GNU Binutils\n2.29 and earlier allows remote attackers to cause an out of bounds heap\nread via a crafted binary file. (CVE-2017-12456)\n\nThe bfd_make_section_with_flags function in section.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29\nand earlier, allows remote attackers to cause a NULL dereference via a\ncrafted file. (CVE-2017-12457)\n\nThe nlm_swap_auxiliary_headers_in function in bfd/nlmcode.h in the Binary\nFile Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils\n2.29 and earlier, allows remote attackers to cause an out of bounds heap\nread via a crafted nlm file. (CVE-2017-12458)\n\nThe bfd_mach_o_read_symtab_strtab function in bfd/mach-o.c in the Binary\nFile Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils\n2.29 and earlier, allows remote attackers to cause an out of bounds heap\nwrite and possibly achieve code execution via a crafted mach-o file.\n(CVE-2017-12459)\n\nThe elf_read_notesfunction in bfd/elf.c in GNU Binutils 2.29 allows remote\nattackers to cause a denial of service (buffer overflow and application\ncrash) or possibly have unspecified other impact via a crafted binary file.\n(CVE-2017-12799)\n\nThe setup_group function in elf.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (NULL pointer dereference and\napplication crash) via a group section that is too small. (CVE-2017-13710)\n\nThe C++ symbol demangler routine in cplus-dem.c in libiberty, as\ndistributed in GNU Binutils 2.29, allows remote attackers to cause a\ndenial of service (excessive memory allocation and application crash) via\na crafted file, as demonstrated by a call from the Binary File Descriptor\n(BFD) library (aka libbfd). (CVE-2017-13716)\n\nThe Binary File Descriptor (BFD) library (aka libbfd), as distributed in\nGNU Binutils 2.29, does not validate the PLT section size, which allows\nremote attackers to cause a denial of service (heap-based buffer over-read\nand application crash) via a crafted ELF file, related to\nelf_i386_get_synthetic_symtab in elf32-i386.c and \nelf_x86_64_get_synthetic_symtab in elf64-x86-64.c. (CVE-2017-13757)\n\nThe decode_line_info function in dwarf2.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows\nremote attackers to cause a denial of service (read_1_byte heap-based\nbuffer over-read and application crash) via a crafted ELF file.\n(CVE-2017-14128)\n\nThe read_section function in dwarf2.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (parse_comp_unit heap-based buffer\nover-read and application crash) via a crafted ELF file. (CVE-2017-14129)\n\nThe _bfd_elf_parse_attributes function in elf-attrs.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29,\nallows remote attackers to cause a denial of service \n(_bfd_elf_attr_strdup heap-based buffer over-read and application crash)\nvia a crafted ELF file. (CVE-2017-14130)\n\nThe process_version_sections function in readelf.c in GNU Binutils 2.29\nallows attackers to cause a denial of service (Integer Overflow, and hang\nbecause of a time-consuming loop) or possibly have unspecified other impact\nvia a crafted binary file with invalid values of ent.vn_next, during\n\"readelf -a\" execution. (CVE-2017-14333)\n\nThe pe_print_idata function in peXXigen.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, mishandles\nHintName vector entries, which allows remote attackers to cause a denial\nof service (heap-based buffer over-read and application crash) via a\ncrafted PE file, related to the bfd_getl16 function. (CVE-2017-14529)\n\nThe *_get_synthetic_symtab functions in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, do not ensure\na unique PLT entry for a symbol, which allows remote attackers to cause a\ndenial of service (heap-based buffer overflow and application crash) or\npossibly have unspecified other impact via a crafted ELF file, related to\nelf32-i386.c and elf64-x86-64.c. (CVE-2017-14729)\n\nThe *_get_synthetic_symtab functions in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, interpret a -1\nvalue as a sorting count instead of an error flag, which allows remote\nattackers to cause a denial of service (integer overflow and application\ncrash) or possibly have unspecified other impact via a crafted ELF file,\nrelated to elf32-i386.c and elf64-x86-64.c. (CVE-2017-14745)\n\n_bfd_elf_slurp_version_tables in elf.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (excessive memory allocation and\napplication crash) via a crafted ELF file. (CVE-2017-14938)\n\ndecode_line_info in dwarf2.c in the Binary File Descriptor (BFD) library\n(aka libbfd), as distributed in GNU Binutils 2.29, mishandles a length\ncalculation, which allows remote attackers to cause a denial of service\n(heap-based buffer over-read and application crash) via a crafted ELF\nfile, related to read_1_byte. (CVE-2017-14939)\n\nscan_unit_for_symbols in dwarf2.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (NULL pointer dereference and\napplication crash) via a crafted ELF file. (CVE-2017-14940)\n\nThe *_get_synthetic_symtab functions in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, mishandle the\nfailure of a certain canonicalization step, which allows remote attackers\nto cause a denial of service (NULL pointer dereference and application\ncrash) via a crafted ELF file, related to elf32-i386.c and elf64-x86-64.c.\n(CVE-2017-14974)\n\ndwarf1.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.29, mishandles pointers, which allows remote\nattackers to cause a denial of service (application crash) or possibly\nhave unspecified other impact via a crafted ELF file, related to\nparse_die and parse_line_table, as demonstrated by a parse_die heap-based\nbuffer over-read. (CVE-2017-15020)\n\nbfd_get_debug_link_info_1 in opncls.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (heap-based buffer over-read and\napplication crash) via a crafted ELF file, related to bfd_getl32.\n(CVE-2017-15021)\n\ndwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.29, does not validate the DW_AT_name data\ntype, which allows remote attackers to cause a denial of service\n(bfd_hash_hash NULL pointer dereference, or out-of-bounds access, and\napplication crash) via a crafted ELF file, related to\nscan_unit_for_symbols and parse_comp_unit. (CVE-2017-15022)\n\nread_formatted_entries in dwarf2.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, does not\nproperly validate the format count, which allows remote attackers to cause\na denial of service (NULL pointer dereference and application crash) via a\ncrafted ELF file, related to concat_filename. (CVE-2017-15023)\n\nfind_abstract_instance_name in dwarf2.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29, allows remote\nattackers to cause a denial of service (infinite recursion and application\ncrash) via a crafted ELF file. (CVE-2017-15024)\n\ndecode_line_info in dwarf2.c in the Binary File Descriptor (BFD) library\n(aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers\nto cause a denial of service (divide-by-zero error and application crash)\nvia a crafted ELF file. (CVE-2017-15025)\n\ndwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.29, miscalculates DW_FORM_ref_addr die refs\nin the case of a relocatable object file, which allows remote attackers to\ncause a denial of service (find_abstract_instance_name invalid memory read,\nsegmentation fault, and application crash). (CVE-2017-15938)\n\ndwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.29, mishandles NULL files in a .debug_line\nfile table, which allows remote attackers to cause a denial of service\n(NULL pointer dereference and application crash) via a crafted ELF file,\nrelated to concat_filename. NOTE: this issue is caused by an incomplete\nfix for CVE-2017-15023. (CVE-2017-15939)\n\nThe elf_object_p function in elfcode.h in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.29.1, has an\nunsigned integer overflow because bfd_size_type multiplication is not used.\nA crafted ELF file allows remote attackers to cause a denial of service\n(application crash) or possibly have unspecified other impact.\n(CVE-2018-6323)\n\nIn GNU Binutils 2.30, there's an integer overflow in the function\nload_specific_debug_section() in objdump.c, which results in malloc()\nwith 0 size. A crafted ELF file allows remote attackers to cause a denial\nof service (application crash) or possibly have unspecified other impact.\n(CVE-2018-6543)\n\nThe bfd_get_debug_link_info_1 function in opncls.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils\n2.30, has an unchecked strnlen operation. Remote attackers could leverage\nthis vulnerability to cause a denial of service (segmentation fault) via\na crafted ELF file. (CVE-2018-6759)\n\nThe elf_parse_notes function in elf.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.30, allows remote\nattackers to cause a denial of service (out-of-bounds read and segmentation\nviolation) via a note with a large alignment. (CVE-2018-6872)\n\nIn the coff_pointerize_aux function in coffgen.c in the Binary File\nDescriptor (BFD) library (aka libbfd), as distributed in GNU Binutils\n2.30, an index is not validated, which allows remote attackers to cause\na denial of service (segmentation fault) or possibly have unspecified\nother impact via a crafted file, as demonstrated by objcopy of a COFF\nobject. (CVE-2018-7208)\n\nThe parse_die function in dwarf1.c in the Binary File Descriptor (BFD)\nlibrary (aka libbfd), as distributed in GNU Binutils 2.30, allows remote\nattackers to cause a denial of service (integer overflow and application\ncrash) via an ELF file with corrupt dwarf1 debug information, as\ndemonstrated by nm. (CVE-2018-7568)\n\ndwarf2.c in the Binary File Descriptor (BFD) library (aka libbfd), as\ndistributed in GNU Binutils 2.30, allows remote attackers to cause a\ndenial of service (integer underflow or overflow, and application crash)\nvia an ELF file with a corrupt DWARF FORM block, as demonstrated by nm.\n(CVE-2018-7569)\n\nThe assign_file_positions_for_non_load_sections function in elf.c in the\nBinary File Descriptor (BFD) library (aka libbfd), as distributed in GNU\nBinutils 2.30, allows remote attackers to cause a denial of service (NULL\npointer dereference and application crash) via an ELF file with a RELRO\nsegment that lacks a matching LOAD segment, as demonstrated by objcopy.\n(CVE-2018-7570)\n\nThe swap_std_reloc_in function in aoutx.h in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows\nremote attackers to cause a denial of service (aout_32_swap_std_reloc_out\nNULL pointer dereference and application crash) via a crafted ELF file,\nas demonstrated by objcopy. (CVE-2018-7642)\n\nThe display_debug_ranges function in dwarf.c in GNU Binutils 2.30 allows\nremote attackers to cause a denial of service (integer overflow and\napplication crash) or possibly have unspecified other impact via a crafted\nELF file, as demonstrated by objdump. (CVE-2018-7643)\n\nThe bfd_section_from_shdr function in elf.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, allows\nremote attackers to cause a denial of service (segmentation fault) via a\nlarge attribute section. (CVE-2018-8945)\n\nprocess_cu_tu_index in dwarf.c in GNU Binutils 2.30 allows remote attackers\nto cause a denial of service (heap-based buffer over-read and application\ncrash) via a crafted binary file, as demonstrated by readelf.\n(CVE-2018-10372)\n\nconcat_filename in dwarf2.c in the Binary File Descriptor (BFD) library\n(aka libbfd), as distributed in GNU Binutils 2.30, allows remote attackers\nto cause a denial of service (NULL pointer dereference and application\ncrash) via a crafted binary file, as demonstrated by nm-new.\n(CVE-2018-10373)\n\nThe _bfd_XX_bfd_copy_private_bfd_data_common function in peXXigen.c in the\nBinary File Descriptor (BFD) library (aka libbfd), as distributed in GNU\nBinutils 2.30, processes a negative Data Directory size with an unbounded\nloop that increases the value of (external_IMAGE_DEBUG_DIRECTORY) *edd so\nthat the address exceeds its own memory region, resulting in an\nout-of-bounds memory write, as demonstrated by objcopy copying private info\nwith _bfd_pex64_bfd_copy_private_bfd_data_common in pex64igen.c.\n(CVE-2018-10534)\n\nThe ignore_section_sym function in elf.c in the Binary File Descriptor\n(BFD) library (aka libbfd), as distributed in GNU Binutils 2.30, does not\nvalidate the output_section pointer in the case of a symtab entry with a\n\"SECTION\" type that has a \"0\" value, which allows remote attackers to\ncause a denial of service (NULL pointer dereference and application crash)\nvia a crafted file, as demonstrated by objcopy. (CVE-2018-10535)\n\nAn issue was discovered in cp-demangle.c in GNU libiberty, as distributed\nin GNU Binutils 2.31. Stack Exhaustion occurs in the C++ demangling\nfunctions provided by libiberty, and there is a stack consumption problem\ncaused by recursive stack frames: cplus_demangle_type,\nd_bare_function_type, d_function_type. (CVE-2018-18484)\n\nAn issue was discovered in cp-demangle.c in GNU libiberty, as distributed\nin GNU Binutils 2.31. There is a stack consumption vulnerability resulting\nfrom infinite recursion in the functions d_name(), d_encoding(), and\nd_local_name() in cp-demangle.c. Remote attackers could leverage this\nvulnerability to cause a denial-of-service via an ELF file, as\ndemonstrated by nm. (CVE-2018-18700)\n\nAn issue was discovered in GNU libiberty, as distributed in GNU Binutils\n2.32. It is a stack consumption issue in d_count_templates_scopes in\ncp-demangle.c after many recursive calls. (CVE-2019-9071)\n\nAn issue was discovered in the Binary File Descriptor (BFD) library (aka\nlibbfd), as distributed in GNU Binutils 2.32. It is an attempted excessive\nmemory allocation in _bfd_elf_slurp_version_tables in elf.c.\n(CVE-2019-9073)\n\nAn issue was discovered in the Binary File Descriptor (BFD) library (aka\nlibbfd), as distributed in GNU Binutils 2.32. It is an out-of-bounds read\nleading to a SEGV in bfd_getl32 in libbfd.c, when called from\npex64_get_runtime_function in pei-x86_64.c. (CVE-2019-9074)\n\nAn issue was discovered in the Binary File Descriptor (BFD) library (aka\nlibbfd), as distributed in GNU Binutils 2.32. It is a heap-based buffer\noverflow in _bfd_archive_64_bit_slurp_armap in archive64.c.\n(CVE-2019-9075)\n\nAn issue was discovered in GNU Binutils 2.32. It is a heap-based buffer\noverflow in process_mips_specific in readelf.c via a malformed MIPS option\nsection. (CVE-2019-9077)\n\nFor more information on the various security issues, read the referenced\ncve.mitre.org links.\n\nFor more information about the other changes and additional features of\nbinutils / gas / ld in this update, see the referenced sourceware.org\nNEWS links.\n","status":"published","published":"2019-05-12T20:58:05Z","modified":"2026-04-16T06:24:13.457855172Z","updated_at":"2026-11-02T15:49:40.793816Z"},{"id":"openSUSE-SU-2024:10651-1","title":"binutils-2.37-1.3 on GA media","description":"These are all security issues fixed in the binutils-2.37-1.3 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:21:04.564666Z","updated_at":"2026-11-02T16:58:34.487567Z"},{"id":"SUSE-SU-2017:3170-1","title":"Security update for binutils","description":"\n\nGNU binutil was updated to the 2.29.1 release, bringing various new features, fixing a lot of bugs and security issues.\n\nFollowing security issues are being addressed by this release:\n\n  * 18750 bsc#1030296 CVE-2014-9939\n  * 20891 bsc#1030585 CVE-2017-7225\n  * 20892 bsc#1030588 CVE-2017-7224\n  * 20898 bsc#1030589 CVE-2017-7223\n  * 20905 bsc#1030584 CVE-2017-7226\n  * 20908 bsc#1031644 CVE-2017-7299\n  * 20909 bsc#1031656 CVE-2017-7300\n  * 20921 bsc#1031595 CVE-2017-7302\n  * 20922 bsc#1031593 CVE-2017-7303\n  * 20924 bsc#1031638 CVE-2017-7301\n  * 20931 bsc#1031590 CVE-2017-7304\n  * 21135 bsc#1030298 CVE-2017-7209 \n  * 21137 bsc#1029909 CVE-2017-6965\n  * 21139 bsc#1029908 CVE-2017-6966\n  * 21156 bsc#1029907 CVE-2017-6969\n  * 21157 bsc#1030297 CVE-2017-7210\n  * 21409 bsc#1037052 CVE-2017-8392\n  * 21412 bsc#1037057 CVE-2017-8393\n  * 21414 bsc#1037061 CVE-2017-8394\n  * 21432 bsc#1037066 CVE-2017-8396\n  * 21440 bsc#1037273 CVE-2017-8421\n  * 21580 bsc#1044891 CVE-2017-9746\n  * 21581 bsc#1044897 CVE-2017-9747\n  * 21582 bsc#1044901 CVE-2017-9748\n  * 21587 bsc#1044909 CVE-2017-9750\n  * 21594 bsc#1044925 CVE-2017-9755\n  * 21595 bsc#1044927 CVE-2017-9756\n  * 21787 bsc#1052518 CVE-2017-12448\n  * 21813 bsc#1052503, CVE-2017-12456, bsc#1052507, CVE-2017-12454, bsc#1052509, CVE-2017-12453, bsc#1052511, CVE-2017-12452, bsc#1052514, CVE-2017-12450, bsc#1052503, CVE-2017-12456, bsc#1052507, CVE-2017-12454, bsc#1052509, CVE-2017-12453, bsc#1052511, CVE-2017-12452, bsc#1052514, CVE-2017-12450\n  * 21933 bsc#1053347 CVE-2017-12799\n  * 21990 bsc#1058480 CVE-2017-14333\n  * 22018 bsc#1056312 CVE-2017-13757\n  * 22047 bsc#1057144 CVE-2017-14129\n  * 22058 bsc#1057149 CVE-2017-14130\n  * 22059 bsc#1057139 CVE-2017-14128\n  * 22113 bsc#1059050 CVE-2017-14529\n  * 22148 bsc#1060599 CVE-2017-14745\n  * 22163 bsc#1061241 CVE-2017-14974\n  * 22170 bsc#1060621 CVE-2017-14729\n\nUpdate to binutils 2.29. [fate#321454, fate#321494, fate#323293]:\n\n  * The MIPS port now supports microMIPS eXtended Physical Addressing (XPA)\n    instructions for assembly and disassembly.\n  * The MIPS port now supports the microMIPS Release 5 ISA for assembly and\n    disassembly.\n  * The MIPS port now supports the Imagination interAptiv MR2 processor,\n    which implements the MIPS32r3 ISA, the MIPS16e2 ASE as well as a couple\n    of implementation-specific regular MIPS and MIPS16e2 ASE instructions.\n  * The SPARC port now supports the SPARC M8 processor, which implements the\n    Oracle SPARC Architecture 2017.\n  * The MIPS port now supports the MIPS16e2 ASE for assembly and disassembly.\n  * Add support for ELF SHF_GNU_MBIND and PT_GNU_MBIND_XXX.\n  * Add support for the wasm32 ELF conversion of the WebAssembly file format.\n  * Add --inlines option to objdump, which extends the --line-numbers option\n    so that inlined functions will display their nesting information.\n  * Add --merge-notes options to objcopy to reduce the size of notes in\n    a binary file by merging and deleting redundant notes.\n  * Add support for locating separate debug info files using the build-id\n    method, where the separate file has a name based upon the build-id of\n    the original file.\n\n- GAS specific:\n\n  * Add support for ELF SHF_GNU_MBIND.\n  * Add support for the WebAssembly file format and wasm32 ELF conversion.\n  * PowerPC gas now checks that the correct register class is used in\n    instructions.  For instance, 'addi %f4,%cr3,%r31' warns three times\n    that the registers are invalid.\n  * Add support for the Texas Instruments PRU processor.\n  * Support for the ARMv8-R architecture and Cortex-R52 processor has been\n    added to the ARM port.\n\n- GNU ld specific:\n\n  * Support for -z shstk in the x86 ELF linker to generate\n    GNU_PROPERTY_X86_FEATURE_1_SHSTK in ELF GNU program properties.\n  * Add support for GNU_PROPERTY_X86_FEATURE_1_SHSTK in ELF GNU program\n    properties in the x86 ELF linker.\n  * Add support for GNU_PROPERTY_X86_FEATURE_1_IBT in ELF GNU program\n    properties in the x86 ELF linker.\n  * Support for -z ibtplt in the x86 ELF linker to generate IBT-enabled\n    PLT.\n  * Support for -z ibt in the x86 ELF linker to generate IBT-enabled\n    PLT as well as GNU_PROPERTY_X86_FEATURE_1_IBT in ELF GNU program\n    properties.\n  * Add support for ELF SHF_GNU_MBIND and PT_GNU_MBIND_XXX.\n  * Add support for ELF GNU program properties.\n  * Add support for the Texas Instruments PRU processor.\n  * When configuring for arc*-*-linux* targets the default linker emulation will\n    change if --with-cpu=nps400 is used at configure time.\n  * Improve assignment of LMAs to orphan sections in some edge cases where a\n    mixture of both AT\u003eLMA_REGION and AT(LMA) are used.\n  * Orphan sections placed after an empty section that has an AT(LMA) will now\n    take an load memory address starting from LMA.\n  * Section groups can now be resolved (the group deleted and the group members\n    placed like normal sections) at partial link time either using the new\n    linker option --force-group-allocation or by placing FORCE_GROUP_ALLOCATION\n    into the linker script.\n\n- Add riscv64 target, tested with gcc7 and downstream newlib 2.4.0\n- Prepare riscv32 target (gh#riscv/riscv-newlib#8)\n- Make compressed debug section handling explicit, disable for\n  old products and enable for gas on all architectures otherwise. [bsc#1029995]\n- Remove empty rpath component removal optimization from to workaround\n  CMake rpath handling.  [bsc#1025282]\n\n\n  Minor security bugs fixed:\n  PR 21147, PR 21148, PR 21149, PR 21150, PR 21151, PR 21155, PR 21158, PR 21159\n\n- Update to binutils 2.28.\n\n  * Add support for locating separate debug info files using the build-id\n    method, where the separate file has a name based upon the build-id of\n    the original file.\n  * This version of binutils fixes a problem with PowerPC VLE 16A and 16D\n    relocations which were functionally swapped, for example,\n    R_PPC_VLE_HA16A performed like R_PPC_VLE_HA16D while R_PPC_VLE_HA16D\n    performed like R_PPC_VLE_HA16A.  This could have been fixed by\n    renumbering relocations, which would keep object files created by an\n    older version of gas compatible with a newer ld.  However, that would\n    require an ABI update, affecting other assemblers and linkers that\n    create and process the relocations correctly.  It is recommended that\n    all VLE object files be recompiled, but ld can modify the relocations\n    if --vle-reloc-fixup is passed to ld.  If the new ld command line\n    option is not used, ld will ld warn on finding relocations inconsistent\n    with the instructions being relocated.\n  * The nm program has a new command line option (--with-version-strings)\n    which will display a symbol's version information, if any, after the\n    symbol's name.\n  * The ARC port of objdump now accepts a -M option to specify the extra\n    instruction class(es) that should be disassembled.\n  * The --remove-section option for objcopy and strip now accepts section\n    patterns starting with an exclamation point to indicate a non-matching\n    section.  A non-matching section is removed from the set of sections\n    matched by an earlier --remove-section pattern.\n  * The --only-section option for objcopy now accepts section patterns\n    starting with an exclamation point to indicate a non-matching section.\n    A non-matching section is removed from the set of sections matched by\n    an earlier --only-section pattern.\n  * New --remove-relocations=SECTIONPATTERN option for objcopy and strip.\n    This option can be used to remove sections containing relocations.\n    The SECTIONPATTERN is the section to which the relocations apply, not\n    the relocation section itself.\n\n- GAS specific:\n\n  * Add support for the RISC-V architecture.\n  * Add support for the ARM Cortex-M23 and Cortex-M33 processors.\n\n- GNU ld specific:\n\n  * The EXCLUDE_FILE linker script construct can now be applied outside of the\n    section list in order for the exclusions to apply over all input sections\n    in the list.\n  * Add support for the RISC-V architecture.\n  * The command line option --no-eh-frame-hdr can now be used in ELF based\n    linkers to disable the automatic generation of .eh_frame_hdr sections.\n  * Add --in-implib=\u003cinfile\u003e to the ARM linker to enable specifying a set of\n    Secure Gateway veneers that must exist in the output import library\n    specified by --out-implib=\u003coutfile\u003e and the address they must have.\n    As such, --in-implib is only supported in combination with --cmse-implib.\n  * Extended the --out-implib=\u003cfile\u003e option, previously restricted to x86 PE\n    targets, to any ELF based target.  This allows the generation of an import\n    library for an ELF executable, which can then be used by another application\n    to link against the executable.\n\n- GOLD specific:\n\n  * Add -z bndplt option (x86-64 only) to support Intel MPX.\n  * Add --orphan-handling option.\n  * Add --stub-group-multi option (PowerPC only).\n  * Add --target1-rel, --target1-abs, --target2 options (Arm only).\n  * Add -z stack-size option.\n  * Add --be8 option (Arm only).\n  * Add HIDDEN support in linker scripts.\n  * Add SORT_BY_INIT_PRIORITY support in linker scripts.\n\n- Other fixes:\n\n  * Fix section alignment on .gnu_debuglink. [bso#21193]\n  * Add s390x to gold_archs.\n  * Fix alignment frags for aarch64 (bsc#1003846)\n  * Call ldconfig for libbfd\n  * Fix an assembler problem with clang on ARM.\n  * Restore monotonically increasing section offsets.\n\n\n- Update to binutils 2.27.\n\n  * Add a configure option, --enable-64-bit-archive, to force use of a\n    64-bit format when creating an archive symbol index.\n  * Add --elf-stt-common= option to objcopy for ELF targets to control\n    whether to convert common symbols to the STT_COMMON type.\n\n- GAS specific:\n\n  * Default to --enable-compressed-debug-sections=gas for Linux/x86 targets.\n  * Add --no-pad-sections to stop the assembler from padding the end of output\n    sections up to their alignment boundary.\n  * Support for the ARMv8-M architecture has been added to the ARM port.\n    Support for the ARMv8-M Security and DSP Extensions has also been added\n    to the ARM port.\n  * ARC backend accepts .extInstruction, .extCondCode, .extAuxRegister, and\n    .extCoreRegister pseudo-ops that allow an user to define custom\n    instructions, conditional codes, auxiliary and core registers.\n  * Add a configure option --enable-elf-stt-common to decide whether ELF\n    assembler should generate common symbols with the STT_COMMON type by\n    default.  Default to no.\n  * New command line option --elf-stt-common= for ELF targets to control\n    whether to generate common symbols with the STT_COMMON type.\n  * Add ability to set section flags and types via numeric values for ELF\n    based targets.\n  * Add a configure option --enable-x86-relax-relocations to decide whether\n    x86 assembler should generate relax relocations by default.  Default to\n    yes, except for x86 Solaris targets older than Solaris 12.\n  * New command line option -mrelax-relocations= for x86 target to control\n    whether to generate relax relocations.\n  * New command line option -mfence-as-lock-add=yes for x86 target to encode\n    lfence, mfence and sfence as 'lock addl $0x0, (%[re]sp)'.\n  * Add assembly-time relaxation option for ARC cpus.\n  * Add --with-cpu=TYPE configure option for ARC gas.  This allows the default\n    cpu type to be adjusted at configure time.\n\n- GOLD specific:\n\n  * Add a configure option --enable-relro to decide whether -z relro should\n    be enabled by default.  Default to yes.\n  * Add support for s390, MIPS, AArch64, and TILE-Gx architectures.\n  * Add support for STT_GNU_IFUNC symbols.\n  * Add support for incremental linking (--incremental).\n\n- GNU ld specific:\n\n  * Add a configure option --enable-relro to decide whether -z relro should\n    be enabled in ELF linker by default.  Default to yes for all Linux\n    targets except FRV, HPPA, IA64 and MIPS.\n  * Support for -z noreloc-overflow in the x86-64 ELF linker to disable\n    relocation overflow check.\n  * Add -z common/-z nocommon options for ELF targets to control whether to\n    convert common symbols to the STT_COMMON type during a relocatable link.\n  * Support for -z nodynamic-undefined-weak in the x86 ELF linker, which\n    avoids dynamic relocations against undefined weak symbols in executable.\n  * The NOCROSSREFSTO command was added to the linker script language.\n  * Add --no-apply-dynamic-relocs to the AArch64 linker to do not apply\n    link-time values for dynamic relocations.\n\n","status":"published","published":"2017-11-30T21:58:48Z","modified":"2026-02-04T03:41:51.070456Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2018:3207-1","title":"Security update for binutils","description":"This update for binutils to 2.31 fixes the following issues:\n\nThese security issues were fixed:\n\n- CVE-2017-15996: readelf allowed remote attackers to cause a denial of service\n  (excessive memory allocation) or possibly have unspecified other impact via a\n  crafted ELF file that triggered a buffer overflow on fuzzed archive header\n  (bsc#1065643).\n- CVE-2017-15939: Binary File Descriptor (BFD) library (aka libbfd) mishandled\n  NULL files in a .debug_line file table, which allowed remote attackers to cause\n  a denial of service (NULL pointer dereference and application crash) via a\n  crafted ELF file, related to concat_filename (bsc#1065689).\n- CVE-2017-15938: the Binary File Descriptor (BFD) library (aka libbfd)\n  miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object\n  file, which allowed remote attackers to cause a denial of service\n  (find_abstract_instance_name invalid memory read, segmentation fault, and\n  application crash) (bsc#1065693).\n- CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (invalid memory access and application crash) or possibly have\n  unspecified other impact via a crafted PE file (bsc#1068640).\n- CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File\n  Descriptor (BFD) library (aka libbfd) did not validate size and offset values\n  in the data dictionary, which allowed remote attackers to cause a denial of\n  service (segmentation violation and application crash) or possibly have\n  unspecified other impact via a crafted PE file (bsc#1068643).\n- CVE-2017-16831: Binary File Descriptor (BFD) library (aka libbfd) did not\n  validate the symbol count, which allowed remote attackers to cause a denial of\n  service (integer overflow and application crash, or excessive memory\n  allocation) or possibly have unspecified other impact via a crafted PE file\n  (bsc#1068887).\n- CVE-2017-16830: The print_gnu_property_note function did not have\n  integer-overflow protection on 32-bit platforms, which allowed remote attackers\n  to cause a denial of service (segmentation violation and application crash) or\n  possibly have unspecified other impact via a crafted ELF file (bsc#1068888).\n- CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File\n  Descriptor (BFD) library (aka libbfd) did not prevent negative pointers, which\n  allowed remote attackers to cause a denial of service (out-of-bounds read and\n  application crash) or possibly have unspecified other impact via a crafted ELF\n  file (bsc#1068950).\n- CVE-2017-16828: The display_debug_frames function allowed remote attackers to\n  cause a denial of service (integer overflow and heap-based buffer over-read,\n  and application crash) or possibly have unspecified other impact via a crafted\n  ELF file (bsc#1069176).\n- CVE-2017-16827: The aout_get_external_symbols function in the Binary File\n  Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a\n  denial of service (slurp_symtab invalid free and application crash) or possibly\n  have unspecified other impact via a crafted ELF file (bsc#1069202).\n- CVE-2018-6323: The elf_object_p function in the Binary File Descriptor (BFD)\n  library (aka libbfd) had an unsigned integer overflow because bfd_size_type\n  multiplication is not used. A crafted ELF file allowed remote attackers to\n  cause a denial of service (application crash) or possibly have unspecified\n  other impact (bsc#1077745).\n- CVE-2018-6543: Prevent integer overflow in the function\n  load_specific_debug_section() which resulted in `malloc()` with 0 size. A\n  crafted ELF file allowed remote attackers to cause a denial of service\n  (application crash) or possibly have unspecified other impact (bsc#1079103).\n- CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File\n  Descriptor (BFD) library (aka libbfd) had an unchecked strnlen operation.\n  Remote attackers could have leveraged this vulnerability to cause a denial of\n  service (segmentation fault) via a crafted ELF file (bsc#1079741).\n- CVE-2018-6872: The elf_parse_notes function in the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (out-of-bounds read and segmentation violation) via a note with a large\n  alignment (bsc#1080556).\n- CVE-2018-7208: In the coff_pointerize_aux function in the Binary File\n  Descriptor (BFD) library (aka libbfd) an index was not validated, which allowed\n  remote attackers to cause a denial of service (segmentation fault) or possibly\n  have unspecified other impact via a crafted file, as demonstrated by objcopy of\n  a COFF object (bsc#1081527).\n- CVE-2018-7570: The assign_file_positions_for_non_load_sections function in\n  the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers\n  to cause a denial of service (NULL pointer dereference and application crash)\n  via an ELF file with a RELRO segment that lacks a matching LOAD segment, as\n  demonstrated by objcopy (bsc#1083528).\n- CVE-2018-7569: The Binary File Descriptor (BFD) library (aka libbfd) allowed\n  remote attackers to cause a denial of service (integer underflow or overflow,\n  and application crash) via an ELF file with a corrupt DWARF FORM block, as\n  demonstrated by nm (bsc#1083532).\n- CVE-2018-8945: The bfd_section_from_shdr function in the Binary File\n  Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a\n  denial of service (segmentation fault) via a large attribute section\n  (bsc#1086608).\n- CVE-2018-7643: The display_debug_ranges function allowed remote attackers to\n  cause a denial of service (integer overflow and application crash) or possibly\n  have unspecified other impact via a crafted ELF file, as demonstrated by\n  objdump (bsc#1086784).\n- CVE-2018-7642: The swap_std_reloc_in function in the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (aout_32_swap_std_reloc_out NULL pointer dereference and application\n  crash) via a crafted ELF file, as demonstrated by objcopy (bsc#1086786).\n- CVE-2018-7568: The parse_die function in the Binary File Descriptor (BFD)\n  library (aka libbfd) allowed remote attackers to cause a denial of service\n  (integer overflow and application crash) via an ELF file with corrupt dwarf1\n  debug information, as demonstrated by nm (bsc#1086788).\n- CVE-2018-10373: concat_filename in the Binary File Descriptor (BFD) library\n  (aka libbfd) allowed remote attackers to cause a denial of service (NULL\n  pointer dereference and application crash) via a crafted binary file, as\n  demonstrated by nm-new (bsc#1090997).\n- CVE-2018-10372: process_cu_tu_index allowed remote attackers to cause a\n  denial of service (heap-based buffer over-read and application crash) via a\n  crafted binary file, as demonstrated by readelf (bsc#1091015).\n- CVE-2018-10535: The ignore_section_sym function in the Binary File Descriptor\n  (BFD) library (aka libbfd) did not validate the output_section pointer in the\n  case of a symtab entry with a 'SECTION' type that has a '0' value, which\n  allowed remote attackers to cause a denial of service (NULL pointer dereference\n  and application crash) via a crafted file, as demonstrated by objcopy\n  (bsc#1091365).\n- CVE-2018-10534: The _bfd_XX_bfd_copy_private_bfd_data_common function in the\n  Binary File Descriptor (BFD) library (aka libbfd) processesed a negative Data\n  Directory size with an unbounded loop that increased the value of\n  (external_IMAGE_DEBUG_DIRECTORY) *edd so that the address exceeded its own\n  memory region, resulting in an out-of-bounds memory write, as demonstrated by\n  objcopy copying private info with _bfd_pex64_bfd_copy_private_bfd_data_common\n  in pex64igen.c (bsc#1091368).\n\nThese non-security issues were fixed:\n\n- The AArch64 port now supports showing disassembly notes which are emitted\n  when inconsistencies are found with the instruction that may result in the\n  instruction being invalid. These can be turned on with the option -M notes\n  to objdump.\n- The AArch64 port now emits warnings when a combination of an instruction and\n  a named register could be invalid.\n- Added O modifier to ar to display member offsets inside an archive\n- The ADR and ADRL pseudo-instructions supported by the ARM assembler\n  now only set the bottom bit of the address of thumb function symbols\n  if the -mthumb-interwork command line option is active.\n- Add --generate-missing-build-notes=[yes|no] option to create (or not) GNU\n  Build Attribute notes if none are present in the input sources.  Add a\n  --enable-generate-build-notes=[yes|no] configure time option to set the\n  default behaviour.  Set the default if the configure option is not used\n  to 'no'.\n- Remove -mold-gcc command-line option for x86 targets.\n- Add -O[2|s] command-line options to x86 assembler to enable alternate\n  shorter instruction encoding.\n- Add support for .nops directive.  It is currently supported only for\n  x86 targets.\n- Speed up direct linking with DLLs for Cygwin and Mingw targets.\n- Add a configure option --enable-separate-code to decide whether\n  -z separate-code should be enabled in ELF linker by default.  Default\n  to yes for Linux/x86 targets. Note that -z separate-code can increase\n  disk and memory size.\n- RISC-V: Fix symbol address problem with versioned symbols \n- Restore riscv64-elf cross prefix via symlinks\n- RISC-V: Don't enable relaxation in relocatable link\n- Prevent linking faiures on i386 with assertion (bsc#1085784)\n- Fix symbol size bug when relaxation deletes bytes\n- Add --debug-dump=links option to readelf and --dwarf=links option to objdump\n  which displays the contents of any .gnu_debuglink or .gnu_debugaltlink\n  sections.\n  Add a --debug-dump=follow-links option to readelf and a --dwarf=follow-links\n  option to objdump which causes indirect links into separate debug info files\n  to be followed when dumping other DWARF sections.\n- Add support for loaction views in DWARF debug line information.\n- Add -z separate-code to generate separate code PT_LOAD segment.\n- Add '-z undefs' command line option as the inverse of the '-z defs' option.\n- Add -z globalaudit command line option to force audit libraries to be run\n  for every dynamic object loaded by an executable - provided that the loader\n  supports this functionality.\n- Tighten linker script grammar around file name specifiers to prevent the use\n  of SORT_BY_ALIGNMENT and SORT_BY_INIT_PRIORITY on filenames.  These would\n  previously be accepted but had no effect.\n- The EXCLUDE_FILE directive can now be placed within any SORT_* directive\n  within input section lists.\n- Fix linker relaxation with --wrap\n- Add arm-none-eabi symlinks (bsc#1074741)\n\nFormer updates of binutils also fixed the following security issues, for which\nthere was not CVE assigned at the time the update was released or no mapping\nbetween code change and CVE existed:\n\n- CVE-2014-9939: Prevent stack buffer overflow when printing bad bytes in Intel\n  Hex objects (bsc#1030296).\n- CVE-2017-7225: The find_nearest_line function in addr2line did not handle the\n  case where the main file name and the directory name are both empty, triggering\n  a NULL pointer dereference and an invalid write, and leading to a program crash\n  (bsc#1030585).\n- CVE-2017-7224: The find_nearest_line function in objdump was vulnerable to an\n  invalid write (of size 1) while disassembling a corrupt binary that contains an\n  empty function name, leading to a program crash (bsc#1030588).\n- CVE-2017-7223: GNU assembler in was vulnerable to a global buffer overflow\n  (of size 1) while attempting to unget an EOF character from the input stream,\n  potentially leading to a program crash (bsc#1030589).\n- CVE-2017-7226: The pe_ILF_object_p function in the Binary File Descriptor\n  (BFD) library (aka libbfd) was vulnerable to a heap-based buffer over-read of\n  size 4049 because it used the strlen function instead of strnlen, leading to\n  program crashes in several utilities such as addr2line, size, and strings. It\n  could lead to information disclosure as well (bsc#1030584).\n- CVE-2017-7299: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  invalid read (of size 8) because the code to emit relocs (bfd_elf_final_link\n  function in bfd/elflink.c) did not check the format of the input file trying to\n  read the ELF reloc section header. The vulnerability leads to a GNU linker (ld)\n  program crash (bsc#1031644).\n- CVE-2017-7300: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  aout_link_add_symbols function in bfd/aoutx.h that is vulnerable to a\n  heap-based buffer over-read (off-by-one) because of an incomplete check for\n  invalid string offsets while loading symbols, leading to a GNU linker (ld)\n  program crash (bsc#1031656).\n- CVE-2017-7302: The Binary File Descriptor (BFD) library (aka libbfd) had a\n  swap_std_reloc_out function in bfd/aoutx.h that is vulnerable to an invalid\n  read (of size 4) because of missing checks for relocs that could not be\n  recognised. This vulnerability caused Binutils utilities like strip to crash\n  (bsc#1031595).\n- CVE-2017-7303: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read (of size 4) because of missing a check (in the\n  find_link function) for null headers attempting to match them. This\n  vulnerability caused Binutils utilities like strip to crash (bsc#1031593).\n- CVE-2017-7301: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  aout_link_add_symbols function in bfd/aoutx.h that has an off-by-one\n  vulnerability because it did not carefully check the string offset. The\n  vulnerability could lead to a GNU linker (ld) program crash (bsc#1031638).\n- CVE-2017-7304: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read (of size 8) because of missing a check (in the\n  copy_special_section_fields function) for an invalid sh_link field attempting\n  to follow it. This vulnerability caused Binutils utilities like strip to crash\n  (bsc#1031590).\n- CVE-2017-8392: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 8 because of missing a check to determine\n  whether symbols are NULL in the _bfd_dwarf2_find_nearest_line function. This\n  vulnerability caused programs that conduct an analysis of binary programs using\n  the libbfd library, such as objdump, to crash (bsc#1037052).\n- CVE-2017-8393: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to a global buffer over-read error because of an assumption made by\n  code that runs for objcopy and strip, that SHT_REL/SHR_RELA sections are always\n  named starting with a .rel/.rela prefix. This vulnerability caused programs\n  that conduct an analysis of binary programs using the libbfd library, such as\n  objcopy and strip, to crash (bsc#1037057).\n- CVE-2017-8394: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 4 due to NULL pointer dereferencing of\n  _bfd_elf_large_com_section. This vulnerability caused programs that conduct an\n  analysis of binary programs using the libbfd library, such as objcopy, to crash\n  (bsc#1037061).\n- CVE-2017-8396: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 1 because the existing reloc offset range\n  tests didn't catch small negative offsets less than the size of the reloc\n  field. This vulnerability caused programs that conduct an analysis of binary\n  programs using the libbfd library, such as objdump, to crash (bsc#1037066).\n- CVE-2017-8421: The function coff_set_alignment_hook in Binary File Descriptor\n  (BFD) library (aka libbfd) had a memory leak vulnerability which can cause\n  memory exhaustion in objdump via a crafted PE file (bsc#1037273).\n- CVE-2017-9746: The disassemble_bytes function in objdump.c allowed remote\n  attackers to cause a denial of service (buffer overflow and application crash)\n  or possibly have unspecified other impact via a crafted binary file, as\n  demonstrated by mishandling of rae insns printing for this file during 'objdump\n  -D' execution (bsc#1044891).\n- CVE-2017-9747: The ieee_archive_p function in the Binary File Descriptor\n  (BFD) library (aka libbfd) might have allowed remote attackers to cause a\n  denial of service (buffer overflow and application crash) or possibly have\n  unspecified other impact via a crafted binary file, as demonstrated by\n  mishandling of this file during 'objdump -D' execution (bsc#1044897).\n- CVE-2017-9748: The ieee_object_p function in the Binary File Descriptor (BFD)\n  library (aka libbfd) might have allowed remote attackers to cause a denial of\n  service (buffer overflow and application crash) or possibly have unspecified\n  other impact via a crafted binary file, as demonstrated by mishandling of this\n  file during 'objdump -D' execution (bsc#1044901).\n- CVE-2017-9750: opcodes/rx-decode.opc lacked bounds checks for certain scale\n  arrays, which allowed remote attackers to cause a denial of service (buffer\n  overflow and application crash) or possibly have unspecified other impact via a\n  crafted binary file, as demonstrated by mishandling of this file during\n  'objdump -D' execution (bsc#1044909).\n- CVE-2017-9755: Not considering the the number of registers for bnd mode\n  allowed remote attackers to cause a denial of service (buffer overflow and\n  application crash) or possibly have unspecified other impact via a crafted\n  binary file, as demonstrated by mishandling of this file during 'objdump -D'\n  execution (bsc#1044925).\n- CVE-2017-9756: The aarch64_ext_ldst_reglist function allowed remote attackers\n  to cause a denial of service (buffer overflow and application crash) or\n  possibly have unspecified other impact via a crafted binary file, as\n  demonstrated by mishandling of this file during 'objdump -D' execution\n  (bsc#1044927).\n- CVE-2017-7209: The dump_section_as_bytes function in readelf accessed a NULL\n  pointer while reading section contents in a corrupt binary, leading to a\n  program crash (bsc#1030298).\n- CVE-2017-6965: readelf wrote to illegal addresses while processing corrupt\n  input files containing symbol-difference relocations, leading to a heap-based\n  buffer overflow (bsc#1029909).\n- CVE-2017-6966: readelf had a use-after-free (specifically read-after-free)\n  error while processing multiple, relocated sections in an MSP430 binary. This\n  is caused by mishandling of an invalid symbol index, and mishandling of state\n  across invocations (bsc#1029908).\n- CVE-2017-6969: readelf was vulnerable to a heap-based buffer over-read while\n  processing corrupt RL78 binaries. The vulnerability can trigger program\n  crashes. It may lead to an information leak as well (bsc#1029907).\n- CVE-2017-7210: objdump was vulnerable to multiple heap-based buffer\n  over-reads (of size 1 and size 8) while handling corrupt STABS enum type\n  strings in a crafted object file, leading to program crash (bsc#1030297).\n  ","status":"published","published":"2018-10-17T14:57:07Z","modified":"2026-02-04T02:32:42.709555Z","updated_at":"2026-11-02T15:53:45.378228Z"},{"id":"SUSE-SU-2018:3207-2","title":"Security update for binutils","description":"This update for binutils to 2.31 fixes the following issues:\n\nThese security issues were fixed:\n\n- CVE-2017-15996: readelf allowed remote attackers to cause a denial of service\n  (excessive memory allocation) or possibly have unspecified other impact via a\n  crafted ELF file that triggered a buffer overflow on fuzzed archive header\n  (bsc#1065643).\n- CVE-2017-15939: Binary File Descriptor (BFD) library (aka libbfd) mishandled\n  NULL files in a .debug_line file table, which allowed remote attackers to cause\n  a denial of service (NULL pointer dereference and application crash) via a\n  crafted ELF file, related to concat_filename (bsc#1065689).\n- CVE-2017-15938: the Binary File Descriptor (BFD) library (aka libbfd)\n  miscalculated DW_FORM_ref_addr die refs in the case of a relocatable object\n  file, which allowed remote attackers to cause a denial of service\n  (find_abstract_instance_name invalid memory read, segmentation fault, and\n  application crash) (bsc#1065693).\n- CVE-2017-16826: The coff_slurp_line_table function the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (invalid memory access and application crash) or possibly have\n  unspecified other impact via a crafted PE file (bsc#1068640).\n- CVE-2017-16832: The pe_bfd_read_buildid function in the Binary File\n  Descriptor (BFD) library (aka libbfd) did not validate size and offset values\n  in the data dictionary, which allowed remote attackers to cause a denial of\n  service (segmentation violation and application crash) or possibly have\n  unspecified other impact via a crafted PE file (bsc#1068643).\n- CVE-2017-16831: Binary File Descriptor (BFD) library (aka libbfd) did not\n  validate the symbol count, which allowed remote attackers to cause a denial of\n  service (integer overflow and application crash, or excessive memory\n  allocation) or possibly have unspecified other impact via a crafted PE file\n  (bsc#1068887).\n- CVE-2017-16830: The print_gnu_property_note function did not have\n  integer-overflow protection on 32-bit platforms, which allowed remote attackers\n  to cause a denial of service (segmentation violation and application crash) or\n  possibly have unspecified other impact via a crafted ELF file (bsc#1068888).\n- CVE-2017-16829: The _bfd_elf_parse_gnu_properties function in the Binary File\n  Descriptor (BFD) library (aka libbfd) did not prevent negative pointers, which\n  allowed remote attackers to cause a denial of service (out-of-bounds read and\n  application crash) or possibly have unspecified other impact via a crafted ELF\n  file (bsc#1068950).\n- CVE-2017-16828: The display_debug_frames function allowed remote attackers to\n  cause a denial of service (integer overflow and heap-based buffer over-read,\n  and application crash) or possibly have unspecified other impact via a crafted\n  ELF file (bsc#1069176).\n- CVE-2017-16827: The aout_get_external_symbols function in the Binary File\n  Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a\n  denial of service (slurp_symtab invalid free and application crash) or possibly\n  have unspecified other impact via a crafted ELF file (bsc#1069202).\n- CVE-2018-6323: The elf_object_p function in the Binary File Descriptor (BFD)\n  library (aka libbfd) had an unsigned integer overflow because bfd_size_type\n  multiplication is not used. A crafted ELF file allowed remote attackers to\n  cause a denial of service (application crash) or possibly have unspecified\n  other impact (bsc#1077745).\n- CVE-2018-6543: Prevent integer overflow in the function\n  load_specific_debug_section() which resulted in `malloc()` with 0 size. A\n  crafted ELF file allowed remote attackers to cause a denial of service\n  (application crash) or possibly have unspecified other impact (bsc#1079103).\n- CVE-2018-6759: The bfd_get_debug_link_info_1 function in the Binary File\n  Descriptor (BFD) library (aka libbfd) had an unchecked strnlen operation.\n  Remote attackers could have leveraged this vulnerability to cause a denial of\n  service (segmentation fault) via a crafted ELF file (bsc#1079741).\n- CVE-2018-6872: The elf_parse_notes function in the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (out-of-bounds read and segmentation violation) via a note with a large\n  alignment (bsc#1080556).\n- CVE-2018-7208: In the coff_pointerize_aux function in the Binary File\n  Descriptor (BFD) library (aka libbfd) an index was not validated, which allowed\n  remote attackers to cause a denial of service (segmentation fault) or possibly\n  have unspecified other impact via a crafted file, as demonstrated by objcopy of\n  a COFF object (bsc#1081527).\n- CVE-2018-7570: The assign_file_positions_for_non_load_sections function in\n  the Binary File Descriptor (BFD) library (aka libbfd) allowed remote attackers\n  to cause a denial of service (NULL pointer dereference and application crash)\n  via an ELF file with a RELRO segment that lacks a matching LOAD segment, as\n  demonstrated by objcopy (bsc#1083528).\n- CVE-2018-7569: The Binary File Descriptor (BFD) library (aka libbfd) allowed\n  remote attackers to cause a denial of service (integer underflow or overflow,\n  and application crash) via an ELF file with a corrupt DWARF FORM block, as\n  demonstrated by nm (bsc#1083532).\n- CVE-2018-8945: The bfd_section_from_shdr function in the Binary File\n  Descriptor (BFD) library (aka libbfd) allowed remote attackers to cause a\n  denial of service (segmentation fault) via a large attribute section\n  (bsc#1086608).\n- CVE-2018-7643: The display_debug_ranges function allowed remote attackers to\n  cause a denial of service (integer overflow and application crash) or possibly\n  have unspecified other impact via a crafted ELF file, as demonstrated by\n  objdump (bsc#1086784).\n- CVE-2018-7642: The swap_std_reloc_in function in the Binary File Descriptor\n  (BFD) library (aka libbfd) allowed remote attackers to cause a denial of\n  service (aout_32_swap_std_reloc_out NULL pointer dereference and application\n  crash) via a crafted ELF file, as demonstrated by objcopy (bsc#1086786).\n- CVE-2018-7568: The parse_die function in the Binary File Descriptor (BFD)\n  library (aka libbfd) allowed remote attackers to cause a denial of service\n  (integer overflow and application crash) via an ELF file with corrupt dwarf1\n  debug information, as demonstrated by nm (bsc#1086788).\n- CVE-2018-10373: concat_filename in the Binary File Descriptor (BFD) library\n  (aka libbfd) allowed remote attackers to cause a denial of service (NULL\n  pointer dereference and application crash) via a crafted binary file, as\n  demonstrated by nm-new (bsc#1090997).\n- CVE-2018-10372: process_cu_tu_index allowed remote attackers to cause a\n  denial of service (heap-based buffer over-read and application crash) via a\n  crafted binary file, as demonstrated by readelf (bsc#1091015).\n- CVE-2018-10535: The ignore_section_sym function in the Binary File Descriptor\n  (BFD) library (aka libbfd) did not validate the output_section pointer in the\n  case of a symtab entry with a 'SECTION' type that has a '0' value, which\n  allowed remote attackers to cause a denial of service (NULL pointer dereference\n  and application crash) via a crafted file, as demonstrated by objcopy\n  (bsc#1091365).\n- CVE-2018-10534: The _bfd_XX_bfd_copy_private_bfd_data_common function in the\n  Binary File Descriptor (BFD) library (aka libbfd) processesed a negative Data\n  Directory size with an unbounded loop that increased the value of\n  (external_IMAGE_DEBUG_DIRECTORY) *edd so that the address exceeded its own\n  memory region, resulting in an out-of-bounds memory write, as demonstrated by\n  objcopy copying private info with _bfd_pex64_bfd_copy_private_bfd_data_common\n  in pex64igen.c (bsc#1091368).\n\nThese non-security issues were fixed:\n\n- The AArch64 port now supports showing disassembly notes which are emitted\n  when inconsistencies are found with the instruction that may result in the\n  instruction being invalid. These can be turned on with the option -M notes\n  to objdump.\n- The AArch64 port now emits warnings when a combination of an instruction and\n  a named register could be invalid.\n- Added O modifier to ar to display member offsets inside an archive\n- The ADR and ADRL pseudo-instructions supported by the ARM assembler\n  now only set the bottom bit of the address of thumb function symbols\n  if the -mthumb-interwork command line option is active.\n- Add --generate-missing-build-notes=[yes|no] option to create (or not) GNU\n  Build Attribute notes if none are present in the input sources.  Add a\n  --enable-generate-build-notes=[yes|no] configure time option to set the\n  default behaviour.  Set the default if the configure option is not used\n  to 'no'.\n- Remove -mold-gcc command-line option for x86 targets.\n- Add -O[2|s] command-line options to x86 assembler to enable alternate\n  shorter instruction encoding.\n- Add support for .nops directive.  It is currently supported only for\n  x86 targets.\n- Speed up direct linking with DLLs for Cygwin and Mingw targets.\n- Add a configure option --enable-separate-code to decide whether\n  -z separate-code should be enabled in ELF linker by default.  Default\n  to yes for Linux/x86 targets. Note that -z separate-code can increase\n  disk and memory size.\n- RISC-V: Fix symbol address problem with versioned symbols \n- Restore riscv64-elf cross prefix via symlinks\n- RISC-V: Don't enable relaxation in relocatable link\n- Prevent linking faiures on i386 with assertion (bsc#1085784)\n- Fix symbol size bug when relaxation deletes bytes\n- Add --debug-dump=links option to readelf and --dwarf=links option to objdump\n  which displays the contents of any .gnu_debuglink or .gnu_debugaltlink\n  sections.\n  Add a --debug-dump=follow-links option to readelf and a --dwarf=follow-links\n  option to objdump which causes indirect links into separate debug info files\n  to be followed when dumping other DWARF sections.\n- Add support for loaction views in DWARF debug line information.\n- Add -z separate-code to generate separate code PT_LOAD segment.\n- Add '-z undefs' command line option as the inverse of the '-z defs' option.\n- Add -z globalaudit command line option to force audit libraries to be run\n  for every dynamic object loaded by an executable - provided that the loader\n  supports this functionality.\n- Tighten linker script grammar around file name specifiers to prevent the use\n  of SORT_BY_ALIGNMENT and SORT_BY_INIT_PRIORITY on filenames.  These would\n  previously be accepted but had no effect.\n- The EXCLUDE_FILE directive can now be placed within any SORT_* directive\n  within input section lists.\n- Fix linker relaxation with --wrap\n- Add arm-none-eabi symlinks (bsc#1074741)\n\nFormer updates of binutils also fixed the following security issues, for which\nthere was not CVE assigned at the time the update was released or no mapping\nbetween code change and CVE existed:\n\n- CVE-2014-9939: Prevent stack buffer overflow when printing bad bytes in Intel\n  Hex objects (bsc#1030296).\n- CVE-2017-7225: The find_nearest_line function in addr2line did not handle the\n  case where the main file name and the directory name are both empty, triggering\n  a NULL pointer dereference and an invalid write, and leading to a program crash\n  (bsc#1030585).\n- CVE-2017-7224: The find_nearest_line function in objdump was vulnerable to an\n  invalid write (of size 1) while disassembling a corrupt binary that contains an\n  empty function name, leading to a program crash (bsc#1030588).\n- CVE-2017-7223: GNU assembler in was vulnerable to a global buffer overflow\n  (of size 1) while attempting to unget an EOF character from the input stream,\n  potentially leading to a program crash (bsc#1030589).\n- CVE-2017-7226: The pe_ILF_object_p function in the Binary File Descriptor\n  (BFD) library (aka libbfd) was vulnerable to a heap-based buffer over-read of\n  size 4049 because it used the strlen function instead of strnlen, leading to\n  program crashes in several utilities such as addr2line, size, and strings. It\n  could lead to information disclosure as well (bsc#1030584).\n- CVE-2017-7299: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  invalid read (of size 8) because the code to emit relocs (bfd_elf_final_link\n  function in bfd/elflink.c) did not check the format of the input file trying to\n  read the ELF reloc section header. The vulnerability leads to a GNU linker (ld)\n  program crash (bsc#1031644).\n- CVE-2017-7300: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  aout_link_add_symbols function in bfd/aoutx.h that is vulnerable to a\n  heap-based buffer over-read (off-by-one) because of an incomplete check for\n  invalid string offsets while loading symbols, leading to a GNU linker (ld)\n  program crash (bsc#1031656).\n- CVE-2017-7302: The Binary File Descriptor (BFD) library (aka libbfd) had a\n  swap_std_reloc_out function in bfd/aoutx.h that is vulnerable to an invalid\n  read (of size 4) because of missing checks for relocs that could not be\n  recognised. This vulnerability caused Binutils utilities like strip to crash\n  (bsc#1031595).\n- CVE-2017-7303: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read (of size 4) because of missing a check (in the\n  find_link function) for null headers attempting to match them. This\n  vulnerability caused Binutils utilities like strip to crash (bsc#1031593).\n- CVE-2017-7301: The Binary File Descriptor (BFD) library (aka libbfd) had an\n  aout_link_add_symbols function in bfd/aoutx.h that has an off-by-one\n  vulnerability because it did not carefully check the string offset. The\n  vulnerability could lead to a GNU linker (ld) program crash (bsc#1031638).\n- CVE-2017-7304: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read (of size 8) because of missing a check (in the\n  copy_special_section_fields function) for an invalid sh_link field attempting\n  to follow it. This vulnerability caused Binutils utilities like strip to crash\n  (bsc#1031590).\n- CVE-2017-8392: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 8 because of missing a check to determine\n  whether symbols are NULL in the _bfd_dwarf2_find_nearest_line function. This\n  vulnerability caused programs that conduct an analysis of binary programs using\n  the libbfd library, such as objdump, to crash (bsc#1037052).\n- CVE-2017-8393: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to a global buffer over-read error because of an assumption made by\n  code that runs for objcopy and strip, that SHT_REL/SHR_RELA sections are always\n  named starting with a .rel/.rela prefix. This vulnerability caused programs\n  that conduct an analysis of binary programs using the libbfd library, such as\n  objcopy and strip, to crash (bsc#1037057).\n- CVE-2017-8394: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 4 due to NULL pointer dereferencing of\n  _bfd_elf_large_com_section. This vulnerability caused programs that conduct an\n  analysis of binary programs using the libbfd library, such as objcopy, to crash\n  (bsc#1037061).\n- CVE-2017-8396: The Binary File Descriptor (BFD) library (aka libbfd) was\n  vulnerable to an invalid read of size 1 because the existing reloc offset range\n  tests didn't catch small negative offsets less than the size of the reloc\n  field. This vulnerability caused programs that conduct an analysis of binary\n  programs using the libbfd library, such as objdump, to crash (bsc#1037066).\n- CVE-2017-8421: The function coff_set_alignment_hook in Binary File Descriptor\n  (BFD) library (aka libbfd) had a memory leak vulnerability which can cause\n  memory exhaustion in objdump via a crafted PE file (bsc#1037273).\n- CVE-2017-9746: The disassemble_bytes function in objdump.c allowed remote\n  attackers to cause a denial of service (buffer overflow and application crash)\n  or possibly have unspecified other impact via a crafted binary file, as\n  demonstrated by mishandling of rae insns printing for this file during 'objdump\n  -D' execution (bsc#1044891).\n- CVE-2017-9747: The ieee_archive_p function in the Binary File Descriptor\n  (BFD) library (aka libbfd) might have allowed remote attackers to cause a\n  denial of service (buffer overflow and application crash) or possibly have\n  unspecified other impact via a crafted binary file, as demonstrated by\n  mishandling of this file during 'objdump -D' execution (bsc#1044897).\n- CVE-2017-9748: The ieee_object_p function in the Binary File Descriptor (BFD)\n  library (aka libbfd) might have allowed remote attackers to cause a denial of\n  service (buffer overflow and application crash) or possibly have unspecified\n  other impact via a crafted binary file, as demonstrated by mishandling of this\n  file during 'objdump -D' execution (bsc#1044901).\n- CVE-2017-9750: opcodes/rx-decode.opc lacked bounds checks for certain scale\n  arrays, which allowed remote attackers to cause a denial of service (buffer\n  overflow and application crash) or possibly have unspecified other impact via a\n  crafted binary file, as demonstrated by mishandling of this file during\n  'objdump -D' execution (bsc#1044909).\n- CVE-2017-9755: Not considering the the number of registers for bnd mode\n  allowed remote attackers to cause a denial of service (buffer overflow and\n  application crash) or possibly have unspecified other impact via a crafted\n  binary file, as demonstrated by mishandling of this file during 'objdump -D'\n  execution (bsc#1044925).\n- CVE-2017-9756: The aarch64_ext_ldst_reglist function allowed remote attackers\n  to cause a denial of service (buffer overflow and application crash) or\n  possibly have unspecified other impact via a crafted binary file, as\n  demonstrated by mishandling of this file during 'objdump -D' execution\n  (bsc#1044927).\n- CVE-2017-7209: The dump_section_as_bytes function in readelf accessed a NULL\n  pointer while reading section contents in a corrupt binary, leading to a\n  program crash (bsc#1030298).\n- CVE-2017-6965: readelf wrote to illegal addresses while processing corrupt\n  input files containing symbol-difference relocations, leading to a heap-based\n  buffer overflow (bsc#1029909).\n- CVE-2017-6966: readelf had a use-after-free (specifically read-after-free)\n  error while processing multiple, relocated sections in an MSP430 binary. This\n  is caused by mishandling of an invalid symbol index, and mishandling of state\n  across invocations (bsc#1029908).\n- CVE-2017-6969: readelf was vulnerable to a heap-based buffer over-read while\n  processing corrupt RL78 binaries. The vulnerability can trigger program\n  crashes. It may lead to an information leak as well (bsc#1029907).\n- CVE-2017-7210: objdump was vulnerable to multiple heap-based buffer\n  over-reads (of size 1 and size 8) while handling corrupt STABS enum type\n  strings in a crafted object file, leading to program crash (bsc#1030297).\n  ","status":"published","published":"2018-10-18T12:51:00Z","modified":"2026-02-04T03:01:48.536142Z","updated_at":"2026-11-02T15:53:45.378228Z"},{"id":"USN-4336-2","title":"binutils vulnerabilities","description":"USN-4336-1 fixed several vulnerabilities in GNU binutils. This update provides\nthe corresponding update for Ubuntu 16.04 ESM.\n\nOriginal advisory details:\n\n It was discovered that GNU binutils contained a large number of security\n issues. If a user or automated system were tricked into processing a\n specially-crafted file, a remote attacker could cause GNU binutils to\n crash, resulting in a denial of service, or possibly execute arbitrary\n code.\n","status":"published","published":"2021-07-21T13:08:04Z","modified":"2026-06-25T13:30:12.686756458Z","updated_at":"2026-11-02T16:58:14.547547Z"},{"id":"USN-4336-3","title":"binutils vulnerabilities","description":"USN-4336-1 fixed several vulnerabilities in GNU. This update provides\nthe corresponding update for Ubuntu 14.04 LTS.\n\nOriginal advisory details:\n\n It was discovered that GNU binutils contained a large number of security\n issues. If a user or automated system were tricked into processing a\n specially-crafted file, a remote attacker could cause GNU binutils to\n crash, resulting in a denial of service, or possibly execute arbitrary\n code.\n","status":"published","published":"2023-08-09T11:09:00Z","modified":"2026-06-29T13:47:54.075875256Z","updated_at":"2026-11-02T16:58:14.547547Z"}]}}