Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-12967

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

Overview

Published
19 Aug 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
5 OS packages
5 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-125

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Photon OS 1 release · 1 package

fixed 1
crash
Photon OS fixes for CVE-2017-12967
ReleasePackageFixed in
4.0 crash +1 8.0.2-1.ph4

Red Hat 1 release · 1 package

wont fix 1
binutils
Red Hat fixes for CVE-2017-12967
ReleasePackageFixed in
7 binutils +1 wont fix

debian 5 releases · 1 package

fixed 4 affected 1
binutils
debian fixes for CVE-2017-12967
ReleasePackageFixed in
11 binutils 2.29-5
12 binutils 2.29-5
13 binutils 2.29-5
14 binutils 2.29-5
9 binutils affected

echo 1 release · 1 package

fixed 1
binutils
echo fixes for CVE-2017-12967
ReleasePackageFixed in
binutils 2.29-5

root.io debian 1 release · 1 package

fixed 1
rootio-binutils
root.io debian fixes for CVE-2017-12967
ReleasePackageFixed in
12 rootio-binutils 2.29-5

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.