# CVE-2009-1429: Command injection in n/a

> Remote attackers can execute arbitrary commands on Symantec Endpoint Protection servers via crafted packets, requiring immediate patching.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8c9c-m8qr-pq2x

## What is CVE-2009-1429?

CVE-2009-1429 is a critical command injection vulnerability in Symantec Endpoint Protection, published on 29 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2009-1429?

It affects 5 products.


Products: Symantec Antivirus, Symantec Antivirus Central Quarantine Server, Symantec Client Security, Symantec Endpoint Protection, Symantec System Center.

## How do I fix CVE-2009-1429?

No fix has been published for CVE-2009-1429 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-1429 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1429 exists.

Public exploit code:

- Symantec (Multiple Products) - Intel Common Base Agent Remote Command Execution (exploitdb)
- Symantec System Center Alert Management System (xfr.exe) Arbitrary Command Execution (metasploit)
- Symantec System Center Alert Management System - 'xfr.exe' Arbitrary Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Symantec Endpoint Protection

- [CVE-2010-0108](https://insights.sbomify.com/CVE-2010-0108/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4953](https://insights.sbomify.com/CVE-2012-4953/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0111](https://insights.sbomify.com/CVE-2010-0111/): Command injection in n/a (critical 9.3)
- [CVE-2011-0688](https://insights.sbomify.com/CVE-2011-0688/): Command injection in n/a (critical 9.3)
- [CVE-2009-1430](https://insights.sbomify.com/CVE-2009-1430/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1429 and fix it if it is affected.

What it is: CVE-2009-1429 is a critical command injection vulnerability in Symantec Endpoint Protection, published on 29 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1429 exists.

Affected product: Symantec Endpoint Protection. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-1429/ (Markdown: https://insights.sbomify.com/CVE-2009-1429/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-1429
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-1429
- OSV: https://osv.dev/vulnerability/CVE-2009-1429

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-1429/
Summaries are generated and may contain mistakes; the official description above is the record.