CVE-2017-9750

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

CVSS 3.07.8High EPSS percentile95th8.1% chance in 30 days CISA KEVNot listedNo confirmed exploitation
Public exploit: 1 source FixVendor fixNo build named by the sources

Published 2017-06-19Updated 2026-05-13Sources: CVE.org, NVD

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record

Check whether your system uses GNU binutils 2.28 (e.g., run objdump --version and confirm the version).
If you are on GNU binutils 2.28, plan an upgrade to a binutils build that includes the fix from Sourceware bug 21587 (the patch for this issue).
If you can’t upgrade immediately, stop running binutils tools (like objdump -D) on untrusted or downloaded binaries until patched.
After upgrading, re-test the same file-processing workflow that previously used objdump to confirm the tool no longer crashes.

Vendor advisory Some work to apply

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

opcodes/rx-decode.opc in GNU Binutils 2.28 lacks bounds checks for certain scale arrays, which allows remote attackers to cause a denial of service (buffer overflow and application crash) or possibly have unspecified other impact via a crafted binary file, as demonstrated by mishandling of this file during "objdump -D" execution.

In plain language

Written by AI from the record

If you’re using GNU binutils 2.28 (for example via tools like objdump), a crafted binary file can crash the tool—so your small business should act to upgrade, especially if you process untrusted files.

CVE-2017-9750 is a bounds-checking flaw in GNU Binutils 2.28’s opcodes/rx-decode.opc that can be triggered when decoding a crafted binary (e.g., during objdump -D), leading to a buffer overflow and application crash via improper handling of scale arrays.

If you're affected

Tool crashes when viewing files
Denial of service during analysis
Potential risk from processing files
Workflow disruption for IT

What is it

This vulnerability is in a developer tool (GNU binutils) that helps examine binary files. If someone hands you a specially crafted file and your system tries to inspect it (for example with objdump -D), the tool can crash because it mishandles internal array sizes. Think of it like a “file scanner” that can be knocked over by a cleverly shaped document.

Who is affected

This matters if your business uses GNU Binutils 2.28, especially if your IT workflow runs tools like objdump -D on files you didn’t author (for example, downloaded binaries, attachments, or third-party packages). It’s primarily a risk when a crafted file can reach the decoding step—typically through someone giving you a malicious binary to analyze or scan.

The reachability gate here is practical: it’s only a problem when your environment runs binutils 2.28 on attacker-controlled binary input (i.e., the crafted file is processed).

How urgent is it

This is an AMBER issue because a public exploit exists and attackers can use a crafted binary to crash the tool. While it’s not listed as a CISA KEV item, the exploitability and rising likelihood signal make it important to address. Act now if you handle untrusted binaries or your pipeline auto-analyzes uploaded/received files.

What to do — in detail

Confirm exposure

Identify the exact installed version of GNU Binutils by running: objdump --version.
If the output shows GNU Binutils 2.28, treat you as affected.

Upgrade path (target the patched build)

Patch availability points to Sourceware bug 21587: https://sourceware.org/bugzilla/show_bug.cgi?id=21587.
Upgrade your binutils package to the version your distro provides that includes the fix for bug 21587.
If you maintain custom tooling/images, rebuild those images with a binutils version that contains the fix referenced in bug 21587.

Workaround if you can’t upgrade yet

Do not run objdump -D (or other binutils decoding steps that load opcodes/rx decoding) on untrusted binaries.
Where possible, quarantine downloaded binaries and only analyze them in a controlled environment until patched.

What to monitor

Look for crashes or abnormal exits in any automated jobs that run objdump / binutils during file analysis.
Review logs for repeated failures tied to specific input files or ingestion batches.

KEV / timeline

Not listed in CISA KEV (no specific CISA due date provided in the findings).

Technical context

Severity and type

Reported as HIGH (CVSS 7.8) with weakness CWE-119 (improper bounds checking).

Mechanism

In GNU Binutils 2.28, opcodes/rx-decode.opc lacks bounds checks for certain scale arrays. When decoding a crafted binary, internal array handling can go out of bounds, leading to a buffer overflow and an application crash.

Attack vector and trigger

The findings describe the issue being demonstrated via mishandling of a crafted file during objdump -D execution.

Exploitation status

A public exploit is available (1 known) based on the findings.
CISA KEV is not listed for this CVE.

Likelihood signal

EPSS is given as a prediction and rising, but it is not used as a deciding public justification because the findings indicate weaponization exists.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS95th

Public exploit

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in

EPSS

8.1% chance of exploitation activity in the next 30 days, which ranks it in the 95th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 67 days before the patch.

2026-09-23EPSS band changemoderate → 0epss band change
2026-09-21EPSS band change0 → moderateepss band change
2026-09-06EPSS band changemoderate → 0epss band change
2026-09-05EPSS band change0 → moderateepss band change
2026-08-31EPSS band changemoderate → 0epss band change
2026-08-29EPSS band changelow → moderate

Affected products

gnuoss-project · USaka g. nu
- binutilsOSS Libraries

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

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

Scored 7.8 by NVD.

How it is reached

Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable