# CVE-2004-2270: Command injection in n/a

> Attackers can execute arbitrary commands as root via unknown vectors in IBM Parallel Environment sample code.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xw98-vm6c-57r4

## What is CVE-2004-2270?

CVE-2004-2270 is a high-severity command injection vulnerability in n/a, published on 19 Jul 2005. 

### Official description

Unknown vulnerability in IBM Parallel Environment (PE) 3.2 and 4.1 allows attackers to execute arbitrary commands as root via unknown vectors in the sample code.

## Which versions are affected by CVE-2004-2270?

It affects 1 product.


Products: Ibm Parallel Environment.

## How do I fix CVE-2004-2270?

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

## Is CVE-2004-2270 being exploited?

There is no known exploitation of CVE-2004-2270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2270 and fix it if it is affected.

What it is: CVE-2004-2270 is a high-severity command injection vulnerability in n/a, published on 19 Jul 2005. 
Exploitation: There is no known exploitation of CVE-2004-2270 in the wild and no public exploit code.

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-2004-2270/ (Markdown: https://insights.sbomify.com/CVE-2004-2270/index.md)
```

## Sources

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

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