CVE-2017-3143

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 18.2%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 18%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

An attacker who is able to send and receive messages to an authoritative DNS server and who has knowledge of a valid TSIG key name for the zone and service being targeted may be able to manipulate BIND into accepting an unauthorized dynamic update. Affects BIND 9.4.0->9.8.8, 9.9.0->9.9.10-P1, 9.10.0->9.10.5-P1, 9.11.0->9.11.1-P1, 9.9.3-S1->9.9.10-S2, 9.10.5-S1->9.10.5-S2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

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
Severity75% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
18%
EPSS %ILE
97%
KEV
Not listed

Published

January 16, 2019

Last Modified

November 21, 2024

References (16)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntubind9 (1:9.10.3.dfsg.P4-10.1ubuntu5.1) @ zesty2026-05-27ubuntu
ubuntubind9 (1:9.8.1.dfsg.P1-4ubuntu0.23) @ precise2026-05-27ubuntu
redhatbind-32:9.8.2-0.62.rc1.el6_9.42017-07-05redhat
redhatbind-32:9.9.4-50.el7_3.12017-07-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 12 ecosystems)
Alpine:v3.3(1)
PackageVulnerable rangeFixed inDependents
bind—9.10.4_p8-r1—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
bind—9.10.4_p8-r1—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
bind—9.10.4_p8-r1—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
bind—9.11.1_p1-r1—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
bind—9.11.3-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-12.4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-12.4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-12.4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bind9—1:9.10.3.dfsg.P4-12.4—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
bind91:9.8.4.dfsg.P1-6+nmu2 ... 1:9.8.4.dfsg.P1-6+nmu2+deb7u9 (19 versions)1:9.8.4.dfsg.P1-6+nmu2+deb7u17—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
bind91:9.9.5.dfsg-9 ... 1:9.9.5.dfsg-9+deb8u9 (13 versions)1:9.9.5.dfsg-9+deb8u12—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
bind91:9.10.3.dfsg.P4-12.31:9.10.3.dfsg.P4-12.3+deb9u1—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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.

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

Frequently asked(5)

What is CVE-2017-3143?
CVE-2017-3143 is a high vulnerability published on January 16, 2019. An attacker who is able to send and receive messages to an authoritative DNS server and who has knowledge of a valid TSIG key name for the zone and service being targeted may be able to manipulate BIND into accepting an unauthorized dynamic update. Affects BIND 9.4.0->9.8.8, 9.9.0->9.9.10-P1,…
When was CVE-2017-3143 disclosed?
CVE-2017-3143 was first published in the National Vulnerability Database on January 16, 2019, 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-3143 actively exploited?
CVE-2017-3143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18% probability of exploitation in the next 30 days, which ranks it in the top 3.0% of all scored CVEs.
What is the CVSS score of CVE-2017-3143?
CVE-2017-3143 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-3143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3143, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-3143?

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

Start Free Scan →Browse All CVEs