# CVE-2008-2157: Command injection in n/a

> Remote attackers can execute arbitrary commands on EMC AlphaStor via a crafted packet to TCP port 3500.

- **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 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3gxc-fc6m-v573

## What is CVE-2008-2157?

CVE-2008-2157 is a critical command injection vulnerability in n/a, published on 29 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

robotd in the Library Manager in EMC AlphaStor 3.1 SP1 for Windows allows remote attackers to execute arbitrary commands via an unspecified string field in a packet to TCP port 3500.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-2157?

It affects 1 product.


Products: Emc Corporation Alphastor.

## How do I fix CVE-2008-2157?

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

## Is CVE-2008-2157 being exploited?

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

Public exploit code:

- EMC AlphaStor Device Manager Arbitrary Command Execution (metasploit)
- EMC AlphaStor Library Manager Arbitrary Command Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2008-2158](https://insights.sbomify.com/CVE-2008-2158/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2157 and fix it if it is affected.

What it is: CVE-2008-2157 is a critical command injection vulnerability in n/a, published on 29 May 2008. 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-2008-2157 exists.

Affected product: n/a. 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-2008-2157/ (Markdown: https://insights.sbomify.com/CVE-2008-2157/index.md)
```

## Sources

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

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