Skip to content
Fencer Intel
critical 9.8

CVE-2017-9430 in the critical feed json

Stack-based buffer overflow in dnstracer through 1.9 allows attackers to cause a denial of service (application crash) or possibly have uns…

published 2017-06-05 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18365

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.4%
EPSS 11.4% chance of exploitation in 30 days, percentile 96%
public exploits
2
Exploit-DB

Summary

Stack-based buffer overflow in dnstracer through 1.9 allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a command line with a long name argument that is mishandled in a strcpy call for argv[0]. An example threat model is a web application that launches dnstracer with an untrusted name string.

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-9430 updated cvss 5.9

dnstracer: Stack-buffer overflow via a long name argument in command line

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

Timeline

  1. First public exploit (EDB-42115)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-42424 DNSTracer 1.9 - Local Buffer Overflow local, 2017-08-03
  • EDB-42115 DNSTracer 1.8.1 - Buffer Overflow (PoC) dos, 2017-06-05

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.