CVE-2015-0235

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 94.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1) gethostbyname or (2) gethostbyname2 function, aka "GHOST."

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
87(Track)
EG Risk 87/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
Severity100% × 45%
Exploitation95% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
95%
EPSS %ILE
100%
KEV
Not listed

Published

January 28, 2015

Last Modified

May 6, 2026

References (180)

Vendor Advisories for CVE-2015-0235(5)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibc6 (2.15-0ubuntu10.10) @ precise2026-07-26ubuntu
redhatrhev-hypervisor6-0:6.6-20150123.1.el6ev2015-02-04redhat
redhatglibc-0:2.12-1.132.el6_5.52015-01-28redhat
redhatglibc-0:2.3.4-2.57.el4.22015-01-28redhat
redhatglibc-0:2.17-55.el7_0.52015-01-27redhat
redhatglibc-0:2.5-123.el5_11.12015-01-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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
glibc—2.18-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glibc—2.18-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glibc—2.18-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glibc—2.18-1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
eglibc2.11.2-10 ... 2.11.3-4 (10 versions)2.11.3-4+deb6u4—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
eglibc2.13-38 ... 2.13-38+deb7u6 (7 versions)2.13-38+deb7u7—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 0× in last 7d / 6× 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 4,370 total refreshes for this CVE.

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

Publicly available exploits

(9 references)

Working exploit code is in the public domain (2 Metasploit modules) (5 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCarm13/ghost_exploit
    First seen Mar 28, 2015

    CVE-2015-0235 EXIM ESTMP GHOST Glibc Gethostbyname() DoS Exploit/PoC

    Open source ↗
  • Exploit-DBEDB-36421✓ verified
    First seen Mar 18, 2015

    Exim - 'GHOST' glibc gethostbyname Buffer Overflow (Metasploit)

    Open source ↗
  • GitHub PoCmakelinux/CVE-2015-0235-workaround
    First seen Feb 2, 2015

    A shared library wrapper with additional checks for vulnerable functions gethostbyname2_r gethostbyname_r (GHOST vulnerability)

    Open source ↗
  • Exploit-DBEDB-35951
    First seen Jan 29, 2015

    Exim ESMTP 4.80 - glibc gethostbyname Denial of Service

    Open source ↗
  • GitHub PoCmikesplain/CVE-2015-0235-cookbook
    First seen Jan 27, 2015

    A chef cookbook to test the GHOST vulnerability

    Open source ↗
  • GitHub PoCaaronfay/CVE-2015-0235-test
    First seen Jan 27, 2015

    Ansible playbook to check vulnerability for CVE-2015-0235

    Open source ↗
  • GitHub PoCfser/ghost-checker
    First seen Jan 27, 2015

    Test wether you're exposed to ghost (CVE-2015-0235). All kudos go to Qualys Security

    Open source ↗
  • Metasploitexploit/linux/smtp/exim_gethostbyname_bof✓ verified
    First seen Jan 27, 2015

    Exim GHOST (glibc gethostbyname) Buffer Overflow

    Open source ↗
  • Metasploitauxiliary/scanner/http/wordpress_ghost_scanner✓ verified
    First seen Jan 1, 2015

    WordPress XMLRPC GHOST Vulnerability Scanner

    Open source ↗

Frequently asked(4)

What is CVE-2015-0235?
CVE-2015-0235 is a high vulnerability published on January 28, 2015. Heap-based buffer overflow in the nsshostnamedigits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1) gethostbyname or (2) gethostbyname2 function, aka "GHOST."
When was CVE-2015-0235 disclosed?
CVE-2015-0235 was first published in the National Vulnerability Database on January 28, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-0235 actively exploited?
CVE-2015-0235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2015-0235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-0235, 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-2015-0235

Explore →

Is Your Infrastructure Affected by CVE-2015-0235?

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

Start Free Scan →Browse All CVEs