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

> Remote attackers can execute arbitrary code on Novell ZENworks Handheld Management servers via unspecified vectors in ZfHSrvr.exe.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pg4v-8j65-gr3m

## What is CVE-2011-2656?

CVE-2011-2656 is a critical code injection vulnerability in n/a, published on 24 Oct 2011. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in ZfHSrvr.exe in Novell ZENworks Handheld Management (ZHM) 7 allows remote attackers to execute arbitrary code via unknown vectors, a different vulnerability than CVE-2011-2655.

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

It affects 1 product.


Products: Novell Zenworks Handheld Management.

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

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

## Is CVE-2011-2656 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0742](https://insights.sbomify.com/CVE-2011-0742/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-2655](https://insights.sbomify.com/CVE-2011-2655/): Other in n/a (critical 9.3)
- [CVE-2010-4299](https://insights.sbomify.com/CVE-2010-4299/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2656 is a critical code injection vulnerability in n/a, published on 24 Oct 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2656 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-2656/ (Markdown: https://insights.sbomify.com/CVE-2011-2656/index.md)
```

## Sources

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

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