# CVE-2011-2397: Command injection in n/a

> Remote attackers can execute arbitrary code on Iron Mountain Connected Backup servers by sending a crafted opcode 13 request.

- **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:** 5 Dec 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9f7g-mcxq-q3vc

## What is CVE-2011-2397?

CVE-2011-2397 is a critical command injection vulnerability in n/a, published on 5 Dec 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Agent service in Iron Mountain Connected Backup 8.4 allows remote attackers to execute arbitrary code via a crafted opcode 13 request that triggers use of the LaunchCompoundFileAnalyzer class to send request data to the System.getRunTime.exec method.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-2397?

It affects 1 product.


Products: Ironmountain Connected Backup.

## How do I fix CVE-2011-2397?

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

## Is CVE-2011-2397 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2397 and fix it if it is affected.

What it is: CVE-2011-2397 is a critical command injection vulnerability in n/a, published on 5 Dec 2011. 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-2011-2397 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-2011-2397/ (Markdown: https://insights.sbomify.com/CVE-2011-2397/index.md)
```

## Sources

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

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