CVE-2018-5740

HIGHNVD 7.58.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 60% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 60%
CISA-KEV: Not listedEPSS PROB: 60%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

"deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS rebinding attacks, a potential method of circumventing the security model used by client browsers. However, a defect in this feature makes it easy, when the feature is in use, to experience an assertion failure in name.c. Affects BIND 9.7.0->9.8.8, 9.9.0->9.9.13, 9.10.0->9.10.8, 9.11.0->9.11.4, 9.12.0->9.12.2, 9.13.0->9.13.2.

CVSS v3
7.5
EG Score
8.3HIGHhigh confidence
EG Risk
66
EG Risk 66/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
Severity83% × 45%
Exploitation60% × 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
60%
EPSS %ILE
99th
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 public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 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

January 16, 2019

Last Modified

November 21, 2024

References (28)

Vendor Advisories for CVE-2018-5740(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulwresd (1:9.10.3.dfsg.P4-8ubuntu1.11) @ xenial2026-05-27ubuntu
ubuntubind9 (1:9.8.1.dfsg.P1-4ubuntu0.26) @ precise2026-05-27ubuntu
redhatbind-32:9.8.2-0.68.rc1.el6_10.12018-08-27redhat
redhatbind-32:9.9.4-61.el7_5.12018-08-27redhat

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

(26 across 26 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.10.8_p1-r0: fixed in 9.10.8_p1-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.11.4_p1-r0: fixed in 9.11.4_p1-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.11.4_p1-r0: fixed in 9.11.4_p1-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
bind—
  • 9.7.0 up to 9.12.2_p1-r0: fixed in 9.12.2_p1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.11.4.P1+dfsg-1: fixed in 1:9.11.4.P1+dfsg-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.11.4.P1+dfsg-1: fixed in 1:9.11.4.P1+dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.11.4.P1+dfsg-1: fixed in 1:9.11.4.P1+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bind9—
  • every version up to 1:9.11.4.P1+dfsg-1: fixed in 1:9.11.4.P1+dfsg-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.9.5.dfsg-9 ... 1:9.9.5.dfsg-9+deb8u9 (17 versions)
  • every version up to 1:9.9.5.dfsg-9+deb8u16: fixed in 1:9.9.5.dfsg-9+deb8u16
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
bind91:9.10.3.dfsg.P4-12.3 ... 1:9.10.3.dfsg.P4-12.3+deb9u9 (10 versions)
  • every version up to 1:9.10.3.dfsg.P4-12.3+deb9u10: fixed in 1:9.10.3.dfsg.P4-12.3+deb9u10
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 3× in last 7d / 21× 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 121 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2018-5740?
CVE-2018-5740 is a high vulnerability published on January 16, 2019. "deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS rebinding attacks, a potential method of circumventing the security model used by client browsers. However, a defect in this feature makes it easy, when the feature is in use, to…
When was CVE-2018-5740 disclosed?
CVE-2018-5740 was first published 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-2018-5740 actively exploited?
CVE-2018-5740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-5740?
CVE-2018-5740 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3 (HIGH).
How do I remediate CVE-2018-5740?
A fix for CVE-2018-5740 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-5740 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-5740

Explore →

Is Your Infrastructure Affected by CVE-2018-5740?

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

Book a Demo →Browse All CVEs