Skip to content
Fencer Intel
critical 9.8

CVE-2017-9109 json

An issue was discovered in adns before 1.5.2.

published 2020-06-18 6 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18047

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

Summary

An issue was discovered in adns before 1.5.2. It fails to ignore apparent answers before the first RR that was found the first time. when this is fixed, the second answer scan finds the same RRs at the first. Otherwise, adns can be confused by interleaving answers for the CNAME target, with the CNAME itself. In that case the answer data structure (on the heap) can be overrun. With this fixed, it prefers to look only at the answer RRs which come after the CNAME, which is at least arguably correct.

Patch / fix

  • gnu adns 1.5.2
  • adns Debian 14, Debian 13, Debian 12 1.6.0-2

debian advisories DEBIAN-CVE-2017-9109

  • adns SLES 11 SP4-LTSS, SLE Point of Sale 11 SP3 1.4-75.3.1
  • adns SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES for SAP 12 SP3 +14 more 1.4-103.3.1

suse advisories SUSE-SU-2020:14399-1SUSE-SU-2020:1612-1

  • adns openSUSE Leap 15.1 1.5.1-lp151.3.3.1

opensuse advisories openSUSE-SU-2020:0827-1

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-9109 updated cvss 9.8

adns: out-of-bounds access when handling apparent answers

  • 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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/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.