# CVE-2012-2290: Code injection in n/a

> Remote attackers can execute arbitrary code on EMC NetWorker Module for Microsoft Applications by sending crafted TCP messages.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 18 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8j7f-hv3h-7vhf

## What is CVE-2012-2290?

CVE-2012-2290 is a critical code injection vulnerability in n/a, published on 18 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The client in EMC NetWorker Module for Microsoft Applications (NMM) 2.2.1, 2.3 before build 122, and 2.4 before build 375 allows remote attackers to execute arbitrary code by sending a crafted message over a TCP communication channel.

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

## Which versions are affected by CVE-2012-2290?

It affects 1 product.


Products: Emc Networker Module for Microsoft Applications.

## How do I fix CVE-2012-2290?

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

## Is CVE-2012-2290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-0913](https://insights.sbomify.com/CVE-2016-0913/): Command injection in n/a (critical 9.8)
- [CVE-2012-2284](https://insights.sbomify.com/CVE-2012-2284/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2290 and fix it if it is affected.

What it is: CVE-2012-2290 is a critical code injection vulnerability in n/a, published on 18 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2290 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-2012-2290/ (Markdown: https://insights.sbomify.com/CVE-2012-2290/index.md)
```

## Sources

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

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