# CVE-2011-2653: Path traversal in n/a

> Remote attackers can execute arbitrary code via directory traversal in Novell ZENworks Asset Management by uploading executable files.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4q43-8hqg-w3px

## What is CVE-2011-2653?

CVE-2011-2653 is a critical path traversal vulnerability in n/a, published on 8 Dec 2011. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the rtrlet component in Novell ZENworks Asset Management (ZAM) 7.5 allows remote attackers to execute arbitrary code by uploading an executable file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Novell Zenworks Asset Management.

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

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

## Is CVE-2011-2653 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2653 exists.

Public exploit code:

- Novell ZENworks Asset Management Remote Execution (metasploit)
- Novell ZENworks Asset Management - Remote Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6299](https://insights.sbomify.com/CVE-2006-6299/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-4933](https://insights.sbomify.com/CVE-2012-4933/): Hardcoded credentials in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2653 is a critical path traversal vulnerability in n/a, published on 8 Dec 2011. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2653 exists.

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

## Sources

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

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