CVE-2005-3252

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 83.6% 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
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 84%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 84%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

Stack-based buffer overflow in the Back Orifice (BO) preprocessor for Snort before 2.4.3 allows remote attackers to execute arbitrary code via a crafted UDP packet.

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

Published

October 18, 2005

Last Modified

April 16, 2026

References (30)

Data Freshness Timeline

(refreshed 1× in last 7d / 1× 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.

  1. 2026-09-10 09:23 UTCEPSS rescore
  2. 2026-07-26 13:27 UTCEG score recompute▲ 7.50
  3. 2026-07-24 14:11 UTCEPSS rescore
  4. 2026-07-23 00:48 UTCEG score recompute
  5. 2026-07-23 00:29 UTCEG score recompute▼ 8.80
  6. 2026-07-22 23:52 UTCEG score recompute▲ 8.80
  7. 2026-07-22 21:32 UTCEG score recompute
  8. 2026-07-15 16:53 UTCEPSS rescore
  9. 2026-07-11 08:22 UTCEPSS rescore
  10. 2026-07-11 08:22 UTCEPSS rescore
  11. 2026-07-02 14:00 UTCEPSS rescore
  12. 2026-07-01 15:01 UTCEPSS rescore
  13. 2026-06-28 04:52 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-23 21:29 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-15 17:44 UTCEPSS rescore
  21. 2026-06-14 23:13 UTCEPSS rescore
  22. 2026-06-14 23:13 UTCEPSS rescore
  23. 2026-06-12 23:08 UTCEPSS rescore
  24. 2026-06-10 22:14 UTCEPSS rescore
  25. 2026-06-10 13:17 UTCEPSS rescore
Show 22 more
  1. 2026-06-06 13:44 UTCEPSS rescore
  2. 2026-06-06 13:44 UTCEPSS rescore
  3. 2026-06-05 22:43 UTCEPSS rescore
  4. 2026-06-05 22:43 UTCEPSS rescore
  5. 2026-06-04 13:09 UTCEPSS rescore
  6. 2026-06-04 13:09 UTCEPSS rescore
  7. 2026-06-01 13:49 UTCEPSS rescore
  8. 2026-06-01 13:49 UTCEPSS rescore
  9. 2026-05-31 11:56 UTCEG score recompute
  10. 2026-05-31 11:56 UTCGHSA enrichment
  11. 2026-05-31 00:13 UTCEPSS rescore
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-26 07:16 UTCEPSS rescore
  17. 2026-05-26 07:16 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-21 22:38 UTCEPSS rescore
  20. 2026-05-20 22:36 UTCEPSS rescore
  21. 2026-05-20 22:36 UTCEPSS rescore
  22. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(6 references)

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

  • Exploit-DBEDB-16834✓ verified
    First seen Jul 3, 2010

    Snort Back Orifice - Pre-Preprocessor Remote (Metasploit)

    Open source ↗
  • Exploit-DBEDB-1314✓ verified
    First seen Nov 11, 2005

    Snort 2.4.2 - Back Orifice Pre-Preprocessor Remote (4)

    Open source ↗
  • Exploit-DBEDB-1313✓ verified
    First seen Nov 11, 2005

    Snort 2.4.2 - Back Orifice Pre-Preprocessor Remote (3)

    Open source ↗
  • Exploit-DBEDB-1272✓ verified
    First seen Oct 25, 2005

    Snort 2.4.2 - Back Orifice Parsing Remote Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-10026✓ verified
    First seen Oct 18, 2005

    Snort 2.4.0 < 2.4.3 - Back Orifice Pre-Preprocessor Remote (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/ids/snortbopre✓ verified
    First seen Oct 18, 2005

    Snort Back Orifice Pre-Preprocessor Buffer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2005-3252?
CVE-2005-3252 is a high vulnerability published on October 18, 2005. Stack-based buffer overflow in the Back Orifice (BO) preprocessor for Snort before 2.4.3 allows remote attackers to execute arbitrary code via a crafted UDP packet.
When was CVE-2005-3252 disclosed?
CVE-2005-3252 was first published in the National Vulnerability Database on October 18, 2005, with the most recent update on April 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-3252 actively exploited?
CVE-2005-3252 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
How do I remediate CVE-2005-3252?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-3252, 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

Explore the affected products and dependency analysis for CVE-2005-3252

Explore →

Is Your Infrastructure Affected by CVE-2005-3252?

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

Start Free Scan →Browse All CVEs