Skip to content
Fencer Intel
medium 6.5

CVE-2017-12967 json

The getsym function in tekhex.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remot…

published 2017-08-19 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-4488

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

The getsym function in tekhex.c in the Binary File Descriptor (BFD) library (aka libbfd), as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (stack-based buffer over-read and application crash) via a malformed tekhex binary.

Patch / fix

  • binutils Debian 14, Debian 13, Debian 12 2.29-5

debian advisories DEBIAN-CVE-2017-12967

  • binutils Ubuntu Pro 16.04 LTS 2.26.1-1ubuntu1~16.04.8+esm1

ubuntu advisories UBUNTU-CVE-2017-12967

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-12967 updated cvss 3.3

binutils: Stack-based buffer over-read in getsym function in tekhex.c

  • Red Hat Enterprise Linux 5 binutils, binutils220 Red Hat Enterprise Linux 6 binutils Red Hat Enterprise Linux 7 binutils
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.