CVE-2017-9109

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.0%
EPSS %ILE
79th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 18, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Sep 29, 2026
Patch available.
generic

[SECURITY] Fedora 32 Update: adns-1.6.0-1.fc32 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/TRVHN3GGVNQWAOL3PWC5FLAV7HUESLZR/
generic

chiark - git - ianmdlvl - adns.git/summary

http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git
generic

adns 1.5.2, adns 1.6.0 - SECURITY FIXES

https://www.chiark.greenend.org.uk/pipermail/adns-announce/2020/000004.html
generic

[SECURITY] Fedora 31 Update: adns-1.6.0-1.fc31 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UGFZ4SPV6KFQK6ZNUZFB5Y32OYFOM5YJ/

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.6.0-2: fixed in 1.6.0-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.6.0-2: fixed in 1.6.0-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.6.0-2: fixed in 1.6.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
adns—
  • every version up to 1.6.0-2: fixed in 1.6.0-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 158 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-10-03 14:21 UTCEPSS rescore
  5. 2026-09-30 14:59 UTCEPSS rescore
  6. 2026-09-30 09:48 UTCEG score recompute
  7. 2026-09-28 13:45 UTCEPSS rescore
  8. 2026-09-27 13:40 UTCEPSS rescore
  9. 2026-09-27 13:40 UTCEPSS rescore
  10. 2026-09-26 22:12 UTCOSV refresh
  11. 2026-09-26 15:53 UTCEPSS rescore
  12. 2026-09-26 00:19 UTCEPSS rescore
  13. 2026-09-24 13:59 UTCEPSS rescore
  14. 2026-09-23 13:42 UTCEPSS rescore
  15. 2026-09-21 20:27 UTCEPSS rescore
  16. 2026-09-19 15:36 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-12 14:56 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-07 15:56 UTCEPSS rescore
  24. 2026-09-07 08:17 UTCOSV refresh
  25. 2026-09-05 15:24 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 13:56 UTCEPSS rescore
  2. 2026-09-04 05:02 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 03:31 UTCEPSS rescore
  6. 2026-08-30 19:13 UTCEPSS rescore
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:41 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-23 00:14 UTCEPSS rescore
  12. 2026-08-21 23:44 UTCEPSS rescore
  13. 2026-08-20 17:31 UTCOSV refresh
  14. 2026-08-19 16:59 UTCEPSS rescore
  15. 2026-08-18 13:43 UTCEPSS rescore
  16. 2026-08-16 14:51 UTCEPSS rescore
  17. 2026-08-16 02:10 UTCEPSS rescore
  18. 2026-08-15 01:26 UTCEPSS rescore
  19. 2026-08-12 13:46 UTCEPSS rescore
  20. 2026-08-09 13:42 UTCEPSS rescore
  21. 2026-08-08 16:32 UTCEPSS rescore
  22. 2026-08-07 16:22 UTCEPSS rescore
  23. 2026-08-06 13:42 UTCEPSS rescore
  24. 2026-08-06 13:42 UTCEPSS rescore
  25. 2026-08-05 19:13 UTCEPSS rescore
  26. 2026-08-05 11:41 UTCOSV refresh
  27. 2026-08-02 02:23 UTCEPSS rescore
  28. 2026-08-02 02:23 UTCEPSS rescore
  29. 2026-08-01 04:12 UTCEPSS rescore
  30. 2026-07-30 16:24 UTCEPSS rescore
  31. 2026-07-30 01:26 UTCEPSS rescore
  32. 2026-07-28 15:32 UTCEPSS rescore
  33. 2026-07-26 14:51 UTCEPSS rescore
  34. 2026-07-26 14:51 UTCEPSS rescore
  35. 2026-07-23 14:15 UTCEPSS rescore
  36. 2026-07-23 01:31 UTCEG score recompute
  37. 2026-07-22 22:11 UTCEG score recompute
  38. 2026-07-22 14:04 UTCEPSS rescore
  39. 2026-07-21 15:21 UTCEPSS rescore
  40. 2026-07-20 17:04 UTCEPSS rescore
  41. 2026-07-20 17:04 UTCEPSS rescore
  42. 2026-07-19 14:28 UTCEPSS rescore
  43. 2026-07-19 14:28 UTCEPSS rescore
  44. 2026-07-19 10:52 UTCOSV refresh
  45. 2026-07-19 02:26 UTCEPSS rescore
  46. 2026-07-19 02:26 UTCEPSS rescore
  47. 2026-07-18 10:01 UTCEPSS rescore
  48. 2026-07-16 16:59 UTCEPSS rescore
  49. 2026-07-16 16:59 UTCEPSS rescore
  50. 2026-07-15 16:55 UTCEPSS rescore
  51. 2026-07-15 16:54 UTCEPSS rescore
  52. 2026-07-15 01:56 UTCEPSS rescore
  53. 2026-07-15 01:56 UTCEPSS rescore
  54. 2026-07-13 22:26 UTCEPSS rescore
  55. 2026-07-13 22:26 UTCEPSS rescore
  56. 2026-07-12 05:43 UTCEPSS rescore
  57. 2026-07-11 08:24 UTCEPSS rescore
  58. 2026-07-09 19:06 UTCEPSS rescore
  59. 2026-07-08 15:11 UTCEPSS rescore
  60. 2026-07-07 13:42 UTCEPSS rescore
  61. 2026-07-06 16:24 UTCEPSS rescore
  62. 2026-07-06 16:24 UTCEPSS rescore
  63. 2026-07-06 02:20 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-05 02:27 UTCEPSS rescore
  66. 2026-07-04 06:28 UTCEPSS rescore
  67. 2026-07-04 06:28 UTCEPSS rescore
  68. 2026-07-02 16:54 UTCEPSS rescore
  69. 2026-07-01 17:31 UTCOSV refresh
  70. 2026-07-01 15:03 UTCEPSS rescore
  71. 2026-06-30 23:19 UTCEPSS rescore
  72. 2026-06-30 23:19 UTCEPSS rescore
  73. 2026-06-29 14:03 UTCEPSS rescore
  74. 2026-06-28 04:53 UTCEPSS rescore
  75. 2026-06-28 04:53 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-9109?
CVE-2017-9109 is a critical vulnerability published on June 18, 2020. 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…
When was CVE-2017-9109 disclosed?
CVE-2017-9109 was first published on June 18, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-9109 actively exploited?
CVE-2017-9109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (79th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-9109?
CVE-2017-9109 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-9109?
A fix for CVE-2017-9109 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-9109

Explore →

Is Your Infrastructure Affected by CVE-2017-9109?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs