CVE-2018-5737

HIGHNVD 5.97.5▲
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 5.9; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 10%CVSS: 5.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.

CVSS v3
5.9
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
10%
EPSS %ILE
95%
KEV
Not listed

Published

January 16, 2019

Last Modified

November 21, 2024

References (8)

Affected Packages

(17 across 17 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
bind—9.12.1_p2-r0—

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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2018-5737?
CVE-2018-5737 is a high vulnerability published on January 16, 2019. A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause…
When was CVE-2018-5737 disclosed?
CVE-2018-5737 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-2018-5737 actively exploited?
CVE-2018-5737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10% probability of exploitation in the next 30 days, which ranks it in the top 4.6% of all scored CVEs.
What is the CVSS score of CVE-2018-5737?
CVE-2018-5737 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5.
How do I remediate CVE-2018-5737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-5737, 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-2018-5737

Explore →

Is Your Infrastructure Affected by CVE-2018-5737?

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

Start Free Scan →Browse All CVEs