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

> Remote attackers can execute arbitrary code via directory traversal in the Heartbeat Web Service upload handler of CA Total Defense Management Server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8xvg-wm2x-mw68

## What is CVE-2011-1654?

CVE-2011-1654 is a high-severity path traversal vulnerability in n/a, published on 15 Apr 2011. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in the Heartbeat Web Service in CA.Itm.Server.ManagementWS.dll in the Management Server in CA Total Defense (TD) r12 before SE2 allows remote attackers to execute arbitrary code via directory traversal sequences in the GUID parameter in an upload request to FileUploadHandler.ashx.

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

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

It affects 1 product.


Products: Broadcom Total Defense.

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

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

## Is CVE-2011-1654 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2667](https://insights.sbomify.com/CVE-2011-2667/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1653](https://insights.sbomify.com/CVE-2011-1653/): SQL injection in n/a (critical 10.0)
- [CVE-2011-1655](https://insights.sbomify.com/CVE-2011-1655/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1654 is a high-severity path traversal vulnerability in n/a, published on 15 Apr 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1654 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-1654/ (Markdown: https://insights.sbomify.com/CVE-2011-1654/index.md)
```

## Sources

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

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