Multiple buffer overflows in Pavuk before 0.9.32 have unknown attack vectors and impact.
CVE-2005-1035
HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — 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: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 1.3% 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
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS v2: 7.5Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v2.0 (legacy)
- 7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 7.5HIGHlow confidence
- EG Risk
- 39EG Risk 39/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 computedSeverity75% × 45%Exploitation1% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 1.3%
- EPSS %ILE
- 68th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · 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
April 5, 2005
Last Modified
June 16, 2026
References (4)
- cve@mitrehttp://secunia.com/advisories/14571
- cve@mitrehttp://sourceforge.net/project/shownotes.php?release_id=313436
- af854a3a-2127-422b-91ae-364da2661108http://secunia.com/advisories/14571
- af854a3a-2127-422b-91ae-364da2661108http://sourceforge.net/project/shownotes.php?release_id=313436
Frequently asked(4)
What is CVE-2005-1035?
CVE-2005-1035 is a high vulnerability published on April 5, 2005. Multiple buffer overflows in Pavuk before 0.9.32 have unknown attack vectors and impact.
When was CVE-2005-1035 disclosed?
CVE-2005-1035 was first published on April 5, 2005, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-1035 actively exploited?
CVE-2005-1035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (68th percentile of EPSS-scored CVEs).
How do I remediate CVE-2005-1035?
No fix for CVE-2005-1035 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2005-1035
Is Your Infrastructure Affected by CVE-2005-1035?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.