Skip to content

CVE-2015-0235

GHOST

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
10.0Critical
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
94.6%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
28 Jan 2015analysed here 12 Nov 2026

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • gnu:glibc
  • oracle:communications_application_session_controller
  • oracle:communications_eagle_application_processor
  • oracle:communications_eagle_lnp_application_processor
  • oracle:communications_lsms
  • oracle:communications_policy_management
  • oracle:communications_session_border_controller
  • oracle:communications_user_data_repository
  • oracle:communications_webrtc_session_controller
  • oracle:exalogic_infrastructure
  • oracle:vm_virtualbox
  • oracle:linux
  • debian:debian_linux
  • redhat:virtualization
  • apple:mac_os_x
  • ibm:pureapplication_system
  • ibm:security_access_manager_for_enterprise_single_sign-on
  • php:php

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. This is an out-of-bounds write, a memory-corruption bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 2 on Exploit-DB · 2 Metasploit modules · 16 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 27 Jan 2015First public exploit or proof of concept
  2. 28 Jan 2015Published2 days later
  3. 6 Aug 2024CVE record last updated3,477 days (about 10 years) later
  4. 12 Nov 2026Analysed by vulneraibility.com828 days (about 2 years) later

CVSS vector

CVSS 2.0 · AV:N/AC:L/Au:N/C:C/I:C/A:C

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.

Common questions

Is CVE-2015-0235 being exploited?

Not confirmed. CVE-2015-0235 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 95% probability of exploitation in the next 30 days.

How severe is CVE-2015-0235?

CVE-2015-0235 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2015-0235?

Yes. A fix has been recorded for CVE-2015-0235. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2015-0235 affect?

CVE-2015-0235 affects gnu:glibc, oracle:communications_application_session_controller, oracle:communications_eagle_application_processor, oracle:communications_eagle_lnp_application_processor, and 14 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

50 references in the CVE record, grouped by the tags the record gives them.

Advisories (21)

Show 15 more

Other links (29)

Show 23 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com