# CVE-2011-0924: Code injection in n/a

> Remote attackers can execute arbitrary script code in HP Data Protector by exploiting insufficient verification of EXEC_CMD file contents.

- **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:** 9 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cw2v-h2mm-6m7m

## What is CVE-2011-0924?

CVE-2011-0924 is a critical code injection vulnerability in n/a, published on 9 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The client in HP Data Protector does not verify the contents of files associated with the EXEC_CMD command, which allows remote attackers to execute arbitrary script code by providing this code with a trusted filename, as demonstrated by omni_chk_ds.sh.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Hp Data Protector.

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

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

## Is CVE-2011-0924 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0921](https://insights.sbomify.com/CVE-2011-0921/): Auth bypass in n/a (critical 10.0)
- [CVE-2011-0922](https://insights.sbomify.com/CVE-2011-0922/): Command injection in n/a (critical 10.0)
- [CVE-2011-0923](https://insights.sbomify.com/CVE-2011-0923/): Code injection in n/a (critical 10.0)
- [CVE-2017-5807](https://insights.sbomify.com/CVE-2017-5807/): Memory corruption in Data Protector (critical 9.8)
- [CVE-2016-2004](https://insights.sbomify.com/CVE-2016-2004/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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