Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
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-9042

binutils: Invalid variable type in readelf.c

Overview

Published
18 May 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
5 OS packages
5 Linux distributions
Yes Fix available

Description

readelf.c in GNU Binutils 2017-04-12 has a "cannot be represented in type long" issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted ELF file.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.0 base score, scored by NVD.

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

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

Weakness: CWE-704

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-9042
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-9042
ReleasePackageFixed in
7 binutils +1 wont fix

debian 5 releases · 1 package

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

echo 1 release · 1 package

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

root.io debian 1 release · 1 package

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

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.