CVE-2015-2305

MEDIUMCVSS v2 · 6.86.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.8 — v2 rates that MEDIUM (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:M/Au:N/C:P/I:P/A:P. 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 8.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
Elevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 8.9%CVSS v2: 6.8Exploit: Elevated riskExposed services: —

A fix is available — apply it.

Integer overflow in the regcomp implementation in the Henry Spencer BSD regex library (aka rxspencer) alpha3.8.g5 on 32-bit platforms, as used in NetBSD through 6.1.5 and other products, might allow context-dependent attackers to execute arbitrary code via a large regular expression that leads to a heap-based buffer overflow.

Internet exposure

The internet-exposure footprint is temporarily unavailable — the KEV-Exposure radar's record for this CVE could not be loaded just now. That is not a finding of zero exposed services; please retry shortly.

CVSS v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.8MEDIUMlow confidence
EG Risk
51
EG Risk 51/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
Severity68% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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
8.9%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

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 unknown (not published for this CVE). 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

March 30, 2015

Last Modified

May 6, 2026

Vendor Advisories for CVE-2015-2305

Vendor advisories for this CVE are temporarily unavailable — the list could not be loaded just now. That is not a sign that none exist; please retry shortly.

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(4)

What is CVE-2015-2305?
CVE-2015-2305 is a medium vulnerability published on March 30, 2015. Integer overflow in the regcomp implementation in the Henry Spencer BSD regex library (aka rxspencer) alpha3.8.g5 on 32-bit platforms, as used in NetBSD through 6.1.5 and other products, might allow context-dependent attackers to execute arbitrary code via a large regular expression that leads to a…
When was CVE-2015-2305 disclosed?
CVE-2015-2305 was first published on March 30, 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-2305 actively exploited?
CVE-2015-2305 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.9% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
How do I remediate CVE-2015-2305?
A fix for CVE-2015-2305 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2015-2305

Explore →

Is Your Infrastructure Affected by CVE-2015-2305?

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