CVE-2009-1429

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 87.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
Trending — 3 sources updated this weekWeaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 87%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 87%CVSS v2: 10.0Exploit: 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.

The Intel LANDesk Common Base Agent (CBA) in Symantec Alert Management System 2 (AMS2), as used in Symantec System Center (SSS); Symantec AntiVirus Server; Symantec AntiVirus Central Quarantine Server; Symantec AntiVirus (SAV) Corporate Edition 9 before 9.0 MR7, 10.0 and 10.1 before 10.1 MR8, and 10.2 before 10.2 MR2; Symantec Client Security (SCS) 2 before 2.0 MR7 and 3 before 3.1 MR8; and Symantec Endpoint Protection (SEP) before 11.0 MR3, allows remote attackers to execute arbitrary commands via a crafted packet whose contents are interpreted as a command to be launched in a new process by the CreateProcessA function.

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

Published

April 29, 2009

Last Modified

April 23, 2026

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-17699✓ verified
    First seen Aug 19, 2011

    Symantec System Center Alert Management System - 'xfr.exe' Arbitrary Command Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-10340✓ verified
    First seen Apr 28, 2009

    Symantec (Multiple Products) - Intel Common Base Agent Remote Command Execution

    Open source ↗
  • Metasploitexploit/windows/antivirus/ams_xfr✓ verified
    First seen Apr 28, 2009

    Symantec System Center Alert Management System (xfr.exe) Arbitrary Command Execution

    Open source ↗

Frequently asked(4)

What is CVE-2009-1429?
CVE-2009-1429 is a high vulnerability published on April 29, 2009. The Intel LANDesk Common Base Agent (CBA) in Symantec Alert Management System 2 (AMS2), as used in Symantec System Center (SSS); Symantec AntiVirus Server; Symantec AntiVirus Central Quarantine Server; Symantec AntiVirus (SAV) Corporate Edition 9 before 9.0 MR7, 10.0 and 10.1 before 10.1 MR8, and…
When was CVE-2009-1429 disclosed?
CVE-2009-1429 was first published in the National Vulnerability Database on April 29, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-1429 actively exploited?
CVE-2009-1429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87% 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-2009-1429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-1429, 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-2009-1429

Explore →

Is Your Infrastructure Affected by CVE-2009-1429?

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