CVE-2012-6275

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 46.5% 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.
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 46%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

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

Multiple stack-based buffer overflows in AntDS.exe in BigAntSoft BigAnt IM Message Server allow remote attackers to have an unspecified impact via (1) the filename header in an SCH request or (2) the userid component in a DUPF request.

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

Published

February 24, 2013

Last Modified

April 29, 2026

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 15× 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-08-21 23:44 UTCEPSS rescore
  2. 2026-08-20 22:50 UTCEPSS rescore
  3. 2026-08-19 16:59 UTCEPSS rescore
  4. 2026-08-18 13:42 UTCEPSS rescore
  5. 2026-08-16 02:09 UTCEPSS rescore
  6. 2026-08-15 01:25 UTCEPSS rescore
  7. 2026-08-12 13:45 UTCEPSS rescore
  8. 2026-08-08 16:31 UTCEPSS rescore
  9. 2026-08-07 16:21 UTCEPSS rescore
  10. 2026-08-06 13:42 UTCEPSS rescore
  11. 2026-08-04 15:04 UTCEPSS rescore
  12. 2026-07-30 01:26 UTCEPSS rescore
  13. 2026-07-28 15:31 UTCEPSS rescore
  14. 2026-07-26 13:47 UTCEG score recompute▲ 10.00
  15. 2026-07-25 14:12 UTCEPSS rescore
  16. 2026-07-23 01:08 UTCEG score recompute▼ 2.70
  17. 2026-07-23 00:12 UTCEG score recompute▲ 2.70
  18. 2026-07-22 21:50 UTCEG score recompute
  19. 2026-07-22 14:04 UTCEPSS rescore
  20. 2026-07-22 14:04 UTCEPSS rescore
  21. 2026-07-21 15:21 UTCEPSS rescore
  22. 2026-07-20 17:03 UTCEPSS rescore
  23. 2026-07-20 17:03 UTCEPSS rescore
  24. 2026-07-19 02:25 UTCEPSS rescore
  25. 2026-07-19 02:25 UTCEPSS rescore
Show 61 more
  1. 2026-07-16 16:58 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-13 22:26 UTCEPSS rescore
  5. 2026-07-13 06:08 UTCEPSS rescore
  6. 2026-07-11 08:23 UTCEPSS rescore
  7. 2026-07-09 19:05 UTCEPSS rescore
  8. 2026-07-04 06:27 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 14:22 UTCEPSS rescore
  18. 2026-06-22 14:22 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:56 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-16 17:49 UTCEPSS rescore
  26. 2026-06-16 17:49 UTCEPSS rescore
  27. 2026-06-15 17:44 UTCEPSS rescore
  28. 2026-06-14 23:14 UTCEPSS rescore
  29. 2026-06-12 23:08 UTCEPSS rescore
  30. 2026-06-11 13:56 UTCEPSS rescore
  31. 2026-06-10 13:18 UTCEPSS rescore
  32. 2026-06-08 14:14 UTCEPSS rescore
  33. 2026-06-07 15:22 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-06 13:45 UTCEPSS rescore
  36. 2026-06-05 22:44 UTCEPSS rescore
  37. 2026-06-05 22:44 UTCEPSS rescore
  38. 2026-06-05 06:08 UTCEPSS rescore
  39. 2026-06-05 06:08 UTCEPSS rescore
  40. 2026-06-02 20:10 UTCEPSS rescore
  41. 2026-06-02 20:10 UTCEPSS rescore
  42. 2026-06-01 13:49 UTCEPSS rescore
  43. 2026-06-01 13:49 UTCEPSS rescore
  44. 2026-05-31 22:28 UTCEPSS rescore
  45. 2026-05-31 22:28 UTCEPSS rescore
  46. 2026-05-31 00:14 UTCEPSS rescore
  47. 2026-05-31 00:14 UTCEPSS rescore
  48. 2026-05-29 13:41 UTCEPSS rescore
  49. 2026-05-29 13:41 UTCEPSS rescore
  50. 2026-05-29 00:49 UTCEG score recompute
  51. 2026-05-29 00:49 UTCGHSA enrichment
  52. 2026-05-28 13:42 UTCEPSS rescore
  53. 2026-05-28 13:42 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-26 07:16 UTCEPSS rescore
  56. 2026-05-26 07:16 UTCEPSS rescore
  57. 2026-05-22 21:15 UTCEPSS rescore
  58. 2026-05-22 21:15 UTCEPSS rescore
  59. 2026-05-22 21:15 UTCEPSS rescore
  60. 2026-05-18 21:29 UTCEPSS rescore
  61. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-24527✓ verified
    First seen Feb 20, 2013

    BigAnt Server 2.97 - SCH / DUPF Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/misc/bigant_server_sch_dupf_bof✓ verified
    First seen Jan 9, 2013

    BigAnt Server 2 SCH And DUPF Buffer Overflow

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2012-6275?
CVE-2012-6275 is a high vulnerability published on February 24, 2013. Multiple stack-based buffer overflows in AntDS.exe in BigAntSoft BigAnt IM Message Server allow remote attackers to have an unspecified impact via (1) the filename header in an SCH request or (2) the userid component in a DUPF request.
When was CVE-2012-6275 disclosed?
CVE-2012-6275 was first published in the National Vulnerability Database on February 24, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-6275 actively exploited?
CVE-2012-6275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
How do I remediate CVE-2012-6275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-6275, 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-2012-6275

Explore →

Is Your Infrastructure Affected by CVE-2012-6275?

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

Start Free Scan →Browse All CVEs