{"id":"CVE-2017-16829","aliases":["BELL-CVE-2017-16829","DEBIAN-CVE-2017-16829","EUVD-2017-8004","GHSA-rpgg-426j-hqcx","SUSE-SU-2018:3170-1","SUSE-SU-2018:3207-1","SUSE-SU-2018:3207-2","SUSE-SU-2023:2485-1","SUSE-SU-2024:0319-1","SUSE-SU-2024:0898-1","SUSE-SU-2024:0899-1","UBUNTU-CVE-2017-16829","openSUSE-SU-2024:10651-1","openSUSE-SU-2024:12745-1"],"status":"published","title":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD...","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","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-07","score":0.01784,"percentile":0.78421,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-125"],"published":"2017-11-15T08:00:00Z","modified":"2026-10-24T10:31:03Z","fixes":[{"ecosystem":"Debian:12","package":"binutils","fixed_in":["2.29.90.20180122-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"binutils","fixed_in":["2.29.90.20180122-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"binutils","fixed_in":["2.29.90.20180122-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.90.20180122-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.90.20180122-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.29.90.20180122-1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-6.3.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.31-6.3.1"}]}],"bundled":25},{"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":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1-2.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1-2.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1-2.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-2.23.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-2.23.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-2.23.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"gdb-testresults","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150400.15.14.4"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP2-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP2","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.2-150100.8.39.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"binutils","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.37-1.3"}]}],"bundled":106},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"gdb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.1-6.1"}]}],"bundled":2}],"products":[{"vendor":"gnu","product":"binutils"}],"references":[{"url":"https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=cf54ebff3b7361989712fd9c0128a9b255578163","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"https://security.gentoo.org/glsa/201811-17","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","advisory"]},{"url":"https://sourceware.org/bugzilla/show_bug.cgi?id=22307","tags":["x_refsource_CONFIRM","x_transferred","Exploit","Issue Tracking","Patch","fix"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16829"},{"url":"https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cf54ebff3b7361989712fd9c0128a9b255578163"},{"url":"https://github.com/advisories/GHSA-rpgg-426j-hqcx"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2017-16829","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-16829","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20183170-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/1075418","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-1/","tags":["advisory"]},{"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/1030296","tags":["report"]},{"url":"https://bugzilla.suse.com/1030297","tags":["report"]},{"url":"https://bugzilla.suse.com/1030298","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/1037052","tags":["report"]},{"url":"https://bugzilla.suse.com/1037057","tags":["report"]},{"url":"https://bugzilla.suse.com/1037061","tags":["report"]},{"url":"https://bugzilla.suse.com/1037066","tags":["report"]},{"url":"https://bugzilla.suse.com/1037273","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/1074741","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2014-9939","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-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-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-8396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8421","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/support/update/announcement/2018/suse-su-20183207-2/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232485-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1192285","tags":["report"]},{"url":"https://bugzilla.suse.com/1207712","tags":["report"]},{"url":"https://bugzilla.suse.com/1210081","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240319-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1211052","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48064","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240898-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20240899-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2017-16829","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-16829","tags":["report"]},{"url":"","tags":["advisory"]},{"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-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-16829","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2017-11-15T08:00:00Z","modified":"2024-08-05T20:35:21.216Z","updated_at":"2026-11-02T14:33:21.142987Z"}],"euvd":[{"id":"EUVD-2017-8004","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2017-11-15T08:00:00Z","modified":"2024-08-05T20:35:21Z","updated_at":"2026-11-03T02:23:11.533108Z"}],"ghsa":[{"id":"GHSA-rpgg-426j-hqcx","title":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD...","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2022-05-14T01:56:34Z","modified":"2025-04-20T03:49:31Z","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-125"],"updated_at":"2026-11-02T15:01:56.152144Z"}],"nvd":[{"id":"CVE-2017-16829","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2017-11-15T08:29:00.437Z","modified":"2026-06-17T01:09:59.073Z","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-125"],"updated_at":"2026-11-02T14:04:08.635428Z"}],"osv":[{"id":"BELL-CVE-2017-16829","title":"CVE-2017-16829 does not affect BellSoft software","status":"withdrawn","published":"2017-11-15T08:29:00Z","modified":"2026-01-26T09:48:29.209386Z","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:28:14.137943Z"},{"id":"CVE-2017-16829","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2017-11-15T08:29:00.437Z","modified":"2026-10-24T10:31:03.483095331Z","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:04.853379Z"},{"id":"DEBIAN-CVE-2017-16829","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"published","published":"2017-11-15T08:29:00.437Z","modified":"2026-09-01T20:03:45.12043114Z","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:28.801885Z"},{"id":"UBUNTU-CVE-2017-16829","description":"The _bfd_elf_parse_gnu_properties function in elf-properties.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29.1, does not prevent negative pointers, which allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a crafted ELF file.","status":"withdrawn","published":"2017-11-15T08:29:00Z","modified":"2025-07-16T07:36:21.404287Z","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:14.563448Z"},{"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":"openSUSE-SU-2024:12745-1","title":"gdb-12.1-6.1 on GA media","description":"These are all security issues fixed in the gdb-12.1-6.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:33:16.106575Z","updated_at":"2026-11-02T16:58:35.751245Z"},{"id":"SUSE-SU-2018:3170-1","title":"Security update for binutils","description":"This update for binutils to version 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- Fix pacemaker libqb problem with section start/stop symbols\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","status":"published","published":"2018-10-16T13:35:47Z","modified":"2026-02-04T03:47:14.50132Z","updated_at":"2026-11-02T15:53:45.378228Z"},{"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":"SUSE-SU-2023:2485-1","title":"Security update for gdb","description":"This update for gdb fixes the following issues:\n\ngdb was updated to 12.1. (jsc#SLE-21561)\n\n* DBX mode is deprecated, and will be removed in GDB 13.\n\n* GDB 12 is the last release of GDB that will support building against\n  Python 2.  From GDB 13, it will only be possible to build GDB itself\n  with Python 3 support.\n\n* Improved C++ template support:\n\n  GDB now treats functions/types involving C++ templates like it does function\n  overloads.  Users may omit parameter lists to set breakpoints on families of\n  template functions, including types/functions composed of multiple template types:\n    (gdb) break template_func(template_1, int)\n  The above will set breakpoints at every function `template_func' where\n  the first function parameter is any template type named `template_1' and\n  the second function parameter is `int'.\n  TAB completion also gains similar improvements.\n\n* New commands:\n\n  - maint set backtrace-on-fatal-signal on|off\n  - maint show backtrace-on-fatal-signal\n\n  This setting is 'on' by default.  When 'on' GDB will print a limited\n  backtrace to stderr in the situation where GDB terminates with a\n  fatal signal.  This only supported on some platforms where the\n  backtrace and backtrace_symbols_fd functions are available.\n\n  - set source open on|off\n  - show source open\n\n  This setting, which is on by default, controls whether GDB will try\n  to open source code files.  Switching this off will stop GDB trying\n  to open and read source code files, which can be useful if the files\n  are located over a slow network connection.\n\n  - set varsize-limit\n  - show varsize-limit\n\n  These are now deprecated aliases for 'set max-value-size' and\n  'show max-value-size'.\n\n  - task apply [all | TASK-IDS...] [FLAG]... COMMAND\n\n  Like 'thread apply', but applies COMMAND to Ada tasks.\n\n  - watch [...] task ID\n\n  Watchpoints can now be restricted to a specific Ada task.\n\n  - maint set internal-error backtrace on|off\n  - maint show internal-error backtrace\n  - maint set internal-warning backtrace on|off\n  - maint show internal-warning backtrace\n\n  GDB can now print a backtrace of itself when it encounters either an\n  internal-error, or an internal-warning.  This is on by default for\n  internal-error and off by default for internal-warning.\n\n  - set logging on|off\n\n  Deprecated and replaced by 'set logging enabled on|off'.\n\n  - set logging enabled on|off\n  - show logging enabled\n\n  These commands set or show whether logging is enabled or disabled.\n\n  - exit\n\n  You can now exit GDB by using the new command 'exit', in addition to\n  the existing 'quit' command.\n\n  - set debug threads on|off\n  - show debug threads\n\n  Print additional debug messages about thread creation and deletion.\n\n  - set debug linux-nat on|off\n  - show debug linux-nat\n\n  These new commands replaced the old 'set debug lin-lwp' and 'show\n  debug lin-lwp' respectively.  Turning this setting on prints debug\n  messages relating to GDB's handling of native Linux inferiors.\n\n  - maint flush source-cache\n\n  Flush the contents of the source code cache.\n\n  - maint set gnu-source-highlight enabled on|off\n  - maint show gnu-source-highlight enabled\n\n  Whether GDB should use the GNU Source Highlight library for adding\n  styling to source code.  When off, the library will not be used, even\n  when available.  When GNU Source Highlight isn't used, or can't add\n  styling to a particular source file, then the Python Pygments\n  library will be used instead.\n\n  - set suppress-cli-notifications (on|off)\n  - show suppress-cli-notifications\n\n  This controls whether printing the notifications is suppressed for CLI.\n  CLI notifications occur when you change the selected context\n  (i.e., the current inferior, thread and/or the frame), or when\n  the program being debugged stops (e.g., because of hitting a\n  breakpoint, completing source-stepping, an interrupt, etc.).\n\n  - set style disassembler enabled on|off\n  - show style disassembler enabled\n\n  If GDB is compiled with Python support, and the Python Pygments\n  package is available, then, when this setting is on, disassembler\n  output will have styling applied.\n\n  - set ada source-charset\n  - show ada source-charset\n\n  Set the character set encoding that is assumed for Ada symbols.  Valid\n  values for this follow the values that can be passed to the GNAT\n  compiler via the '-gnati' option.  The default is ISO-8859-1.\n\n* Changed commands:\n\n  - print\n\n  Printing of floating-point values with base-modifying formats like\n  /x has been changed to display the underlying bytes of the value in\n  the desired base.  This was GDB's documented behavior, but was never\n  implemented correctly.\n\n  - maint packet\n\n  This command can now print a reply, if the reply includes\n  non-printable characters.  Any non-printable characters are printed\n  as escaped hex, e.g. \\x?? where '??' is replaces with the value of\n  the non-printable character.\n\n  - clone-inferior\n  The clone-inferior command now ensures that the TTY, CMD and ARGS\n  settings are copied from the original inferior to the new one.\n  All modifications to the environment variables done using the 'set\n  environment' or 'unset environment' commands are also copied to the new\n  inferior.\n\n  - set debug lin-lwp on|off\n  - show debug lin-lwp\n\n  These commands have been removed from GDB.  The new command 'set\n  debug linux-nat' and 'show debug linux-nat' should be used\n  instead.\n\n  - info win\n\n  This command now includes information about the width of the tui\n  windows in its output.\n\n* GDB's Ada parser now supports an extension for specifying the exact\n  byte contents of a floating-point literal.  This can be useful for\n  setting floating-point registers to a precise value without loss of\n  precision.  The syntax is an extension of the based literal syntax.\n  Use, e.g., '16lf#0123abcd#' -- the number of 'l's controls the width\n  of the floating-point type, and the 'f' is the marker for floating\n  point.\n\n* MI changes:\n\n ** The '-add-inferior' with no option flags now inherits the\n    connection of the current inferior, this restores the behaviour of\n    GDB as it was prior to GDB 10.\n\n ** The '-add-inferior' command now accepts a '--no-connection'\n    option, which causes the new inferior to start without a\n    connection.\n\n* Python API:\n\n  ** New function gdb.add_history(), which takes a gdb.Value object\n     and adds the value it represents to GDB's history list.  An\n     integer, the index of the new item in the history list, is\n     returned.\n\n  ** New function gdb.history_count(), which returns the number of\n     values in GDB's value history.\n\n  ** New gdb.events.gdb_exiting event.  This event is called with a\n     gdb.GdbExitingEvent object which has the read-only attribute\n     'exit_code', which contains the value of the GDB exit code.  This\n     event is triggered once GDB decides it is going to exit, but\n     before GDB starts to clean up its internal state.\n\n  ** New function gdb.architecture_names(), which returns a list\n     containing all of the possible Architecture.name() values.  Each\n     entry is a string.\n\n  ** New function gdb.Architecture.integer_type(), which returns an\n     integer type given a size and a signed-ness.\n\n  ** New gdb.TargetConnection object type that represents a connection\n     (as displayed by the 'info connections' command).  A sub-class,\n     gdb.RemoteTargetConnection, is used to represent 'remote' and\n     'extended-remote' connections.\n\n  ** The gdb.Inferior type now has a 'connection' property which is an\n     instance of gdb.TargetConnection, the connection used by this\n     inferior.  This can be None if the inferior has no connection.\n\n  ** New 'gdb.events.connection_removed' event registry, which emits a\n     'gdb.ConnectionEvent' when a connection is removed from GDB.\n     This event has a 'connection' property, a gdb.TargetConnection\n     object for the connection being removed.\n\n  ** New gdb.connections() function that returns a list of all\n     currently active connections.\n\n  ** New gdb.RemoteTargetConnection.send_packet(PACKET) method.  This\n     is equivalent to the existing 'maint packet' CLI command; it\n     allows a user specified packet to be sent to the remote target.\n\n  ** New function gdb.host_charset(), returns a string, which is the\n     name of the current host charset.\n\n  ** New gdb.set_parameter(NAME, VALUE).  This sets the gdb parameter\n     NAME to VALUE.\n\n  ** New gdb.with_parameter(NAME, VALUE).  This returns a context\n     manager that temporarily sets the gdb parameter NAME to VALUE,\n     then resets it when the context is exited.\n\n  ** The gdb.Value.format_string method now takes a 'styling'\n     argument, which is a boolean.  When true, the returned string can\n     include escape sequences to apply styling.  The styling will only\n     be present if styling is otherwise turned on in GDB (see 'help\n     set styling').  When false, which is the default if the argument\n     is not given, then no styling is applied to the returned string.\n\n  ** New read-only attribute gdb.InferiorThread.details, which is\n     either a string, containing additional, target specific thread\n     state information, or None, if there is no such additional\n     information.\n\n  ** New read-only attribute gdb.Type.is_scalar, which is True for\n     scalar types, and False for all other types.\n\n  ** New read-only attribute gdb.Type.is_signed.  This attribute\n     should only be read when Type.is_scalar is True, and will be True\n     for signed types, and False for all other types.  Attempting to\n     read this attribute for non-scalar types will raise a ValueError.\n\n  ** It is now possible to add GDB/MI commands implemented in Python.\n\n- Update libipt to v2.0.5.\n\n- CVE-2018-7208: Fixed improper bounds check in coffgen.c:coff_pointerize_aux() that allowed for denial of service when parsing a crafted COFF file (bsc#1081527).\n- CVE-2017-16829: Fixed possible remote denial of service via the _bfd_elf_parse_gnu_properties() function in elf-properties.c (bsc#1068950).\n\nBug fixes:\n\n- Fixed license (bsc#1210081).\n- Advertises RHEL version support status (bsc#1207712).\n- Fixed crashes while debugging a clang-cpp app (bsc#1192285).\n","status":"published","published":"2023-06-12T06:54:40Z","modified":"2026-02-04T04:15:10.580729Z","updated_at":"2026-11-02T15:53:53.019382Z"},{"id":"SUSE-SU-2024:0319-1","title":"Security update for gdb","description":"This update for gdb fixes the following issues:\n\n- Drop libdebuginfod1 BuildRequires/Recommends. The former isn't\n  needed because there's a build requirement on libdebuginfod-devel\n  already, which will pull the shared library. And the latter,\n  because it's bogus since RPM auto generated dependency will take\n  care of that requirement.\n\ngdb was released in 13.2:\n\n* This version of GDB includes the following changes and enhancements:\n\n  * Support for the following new targets has been added in both GDB and GDBserver:\n\n        * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*\n        * GNU/Linux/CSKY (gdbserver) csky*-*linux* \n\n  * The Windows native target now supports target async.\n  * Floating-point support has now been added on LoongArch GNU/Linux.\n  * New commands:\n\n        * set print nibbles [on|off]\n        * show print nibbles\n\n        * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.\n          Various styling-related commands. See the gdb/NEWS file for more details.\n          Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. \n\n  * Python API improvements:\n\n          * New Python API for instruction disassembly.\n\n          * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.\n          * New Python type gdb.BreakpointLocation.\n          * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '\n          * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.\n          * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.\n          * New method gdb.Frame.language that returns the name of the frame's language.\n          * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.\n          * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.\n          * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. \n   * GDB/MI changes:\n\n          * MI version 1 is deprecated, and will be removed in GDB 14.\n          * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. \n\n   * Miscellaneous improvements:\n\n          * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.\n          * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.\n          * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.\n          * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.\n          * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.\n\n          * A new format '/b' has been introduce to provide the old behavior of '/r'.\n          * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.\n          * It is now possible to use the 'document' command to document user-defined commands.\n          * Support for memory tag data for AArch64 MTE. \n\n   * Support Removal notices:\n\n          * DBX mode has been removed.\n          * Support for building against Python version 2 has been removed. It is now only possible to build GDB against Python 3.\n          * Support for the following commands has been removed:\n\n          * set debug aix-solib on|off\n          * show debug aix-solib\n          * set debug solib-frv on|off\n          * show debug solib-frv\n\n          * Use the 'set/show debug solib' commands instead. \n\nSee the NEWS file for a more complete and detailed list of what this release includes. \n","status":"published","published":"2024-02-20T16:52:21Z","modified":"2026-02-04T02:54:00.812339Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0898-1","title":"Security update for gdb","description":"This update for gdb fixes the following issues:\n\n- Drop libdebuginfod1 BuildRequires/Recommends. The former isn't\n  needed because there's a build requirement on libdebuginfod-devel\n  already, which will pull the shared library. And the latter,\n  because it's bogus since RPM auto generated dependency will take\n  care of that requirement.\n\ngdb was released in 13.2:\n\n* This version of GDB includes the following changes and enhancements:\n\n  * Support for the following new targets has been added in both GDB and GDBserver:\n\n        * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*\n        * GNU/Linux/CSKY (gdbserver) csky*-*linux* \n\n  * The Windows native target now supports target async.\n  * Floating-point support has now been added on LoongArch GNU/Linux.\n  * New commands:\n\n        * set print nibbles [on|off]\n        * show print nibbles\n\n        * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.\n          Various styling-related commands. See the gdb/NEWS file for more details.\n          Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. \n\n  * Python API improvements:\n\n          * New Python API for instruction disassembly.\n\n          * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.\n          * New Python type gdb.BreakpointLocation.\n          * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '\n          * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.\n          * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.\n          * New method gdb.Frame.language that returns the name of the frame's language.\n          * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.\n          * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.\n          * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. \n   * GDB/MI changes:\n\n          * MI version 1 is deprecated, and will be removed in GDB 14.\n          * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. \n\n   * Miscellaneous improvements:\n\n          * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.\n          * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.\n          * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.\n          * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.\n          * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.\n\n          * A new format '/b' has been introduce to provide the old behavior of '/r'.\n          * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.\n          * It is now possible to use the 'document' command to document user-defined commands.\n          * Support for memory tag data for AArch64 MTE. \n\n   * Support Removal notices:\n\n          * DBX mode has been removed.\n          * Support for building against Python version 2 has been removed. It is now only possible to build GDB against Python 3.\n          * Support for the following commands has been removed:\n\n          * set debug aix-solib on|off\n          * show debug aix-solib\n          * set debug solib-frv on|off\n          * show debug solib-frv\n\n          * Use the 'set/show debug solib' commands instead. \n\nSee the NEWS file for a more complete and detailed list of what this release includes. \n","status":"published","published":"2024-03-14T15:05:17Z","modified":"2026-02-04T04:17:05.554581Z","updated_at":"2026-11-02T15:53:54.239786Z"},{"id":"SUSE-SU-2024:0899-1","title":"Security update for gdb","description":"This update for gdb fixes the following issues:\n\n- Drop libdebuginfod1 BuildRequires/Recommends. The former isn't\n  needed because there's a build requirement on libdebuginfod-devel\n  already, which will pull the shared library. And the latter,\n  because it's bogus since RPM auto generated dependency will take\n  care of that requirement.\n\ngdb was released in 13.2:\n\n* This version of GDB includes the following changes and enhancements:\n\n  * Support for the following new targets has been added in both GDB and GDBserver:\n\n        * GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*\n        * GNU/Linux/CSKY (gdbserver) csky*-*linux* \n\n  * The Windows native target now supports target async.\n  * Floating-point support has now been added on LoongArch GNU/Linux.\n  * New commands:\n\n        * set print nibbles [on|off]\n        * show print nibbles\n\n        * This controls whether the 'print/t' command will display binary values in groups of four bits, known as 'nibbles'. The default is 'off'.\n          Various styling-related commands. See the gdb/NEWS file for more details.\n          Various maintenance commands. These are normally aimed at GDB experts or developers. See the gdb/NEWS file for more details. \n\n  * Python API improvements:\n\n          * New Python API for instruction disassembly.\n\n          * The new attribute 'locations' of gdb.Breakpoint returns a list of gdb.BreakpointLocation objects specifying the locations where the breakpoint is inserted into the debuggee.\n          * New Python type gdb.BreakpointLocation.\n          * New function gdb.format_address(ADDRESS, PROGSPACE, ARCHITECTURE) that formats ADDRESS as 'address '\n          * New function gdb.current_language that returns the name of the current language. Unlike gdb.parameter('language'), this will never return 'auto'.\n          * New function gdb.print_options that returns a dictionary of the prevailing print options, in the form accepted by gdb.Value.format_string.\n          * New method gdb.Frame.language that returns the name of the frame's language.\n          * gdb.Value.format_string now uses the format provided by 'print', if it is called during a 'print' or other similar operation.\n          * gdb.Value.format_string now accepts the 'summary' keyword. This can be used to request a shorter representation of a value, the way that 'set print frame-arguments scalars' does.\n          * The gdb.register_window_type method now restricts the set of acceptable window names. The first character of a window's name must start with a character in the set [a-zA-Z], every subsequent character of a window's name must be in the set [-_.a-zA-Z0-9]. \n   * GDB/MI changes:\n\n          * MI version 1 is deprecated, and will be removed in GDB 14.\n          * The async record stating the stopped reason 'breakpoint-hit' now contains an optional field locno. \n\n   * Miscellaneous improvements:\n\n          * gdb now supports zstd compressed debug sections (ELFCOMPRESS_ZSTD) for ELF.\n          * New convenience variable $_inferior_thread_count contains the number of live threads in the current inferior.\n          * New convenience variables $_hit_bpnum and $_hit_locno, set to the breakpoint number and the breakpoint location number of the breakpoint last hit.\n          * The 'info breakpoints' now displays enabled breakpoint locations of disabled breakpoints as in the 'y-' state.\n          * The format of 'disassemble /r' and 'record instruction-history /r' has changed to match the layout of GNU objdump when disassembling.\n\n          * A new format '/b' has been introduce to provide the old behavior of '/r'.\n          * The TUI no longer styles the source and assembly code highlighted by the current position indicator by default. You can however re-enable styling using the new 'set style tui-current-position' command.\n          * It is now possible to use the 'document' command to document user-defined commands.\n          * Support for memory tag data for AArch64 MTE. \n\n   * Support Removal notices:\n\n          * DBX mode has been removed.\n          * Support for building against Python version 2 has been removed. It is now only possible to build GDB against Python 3.\n          * Support for the following commands has been removed:\n\n          * set debug aix-solib on|off\n          * show debug aix-solib\n          * set debug solib-frv on|off\n          * show debug solib-frv\n\n          * Use the 'set/show debug solib' commands instead. \n\nSee the NEWS file for a more complete and detailed list of what this release includes. \n","status":"published","published":"2024-03-14T15:09:54Z","modified":"2025-05-02T04:29:44.737939Z","updated_at":"2026-11-02T15:53:54.239786Z"}]}}