# CVE-2005-1970: Command injection in n/a

> Local attackers with physical access can execute arbitrary commands via Caller Properties if Launch with Windows is enabled.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pp87-gx9v-qm5r

## What is CVE-2005-1970?

CVE-2005-1970 is a high-severity command injection vulnerability in n/a, published on 14 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Symantec pcAnywhere 10.5x and 11.x before 11.5, with "Launch with Windows" enabled, allows local users with physical access to execute arbitrary commands via the Caller Properties feature.

## Which versions are affected by CVE-2005-1970?

It affects 1 product.


Products: Symantec Pcanywhere.

## How do I fix CVE-2005-1970?

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

## Is CVE-2005-1970 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3478](https://insights.sbomify.com/CVE-2011-3478/): Auth bypass in n/a (critical 10.0)
- [CVE-2000-0300](https://insights.sbomify.com/CVE-2000-0300/): Weak cryptography in n/a (critical 10.0)
- [CVE-2005-3934](https://insights.sbomify.com/CVE-2005-3934/): Memory corruption in n/a (high 7.8)
- [CVE-2006-3784](https://insights.sbomify.com/CVE-2006-3784/): Privilege escalation in n/a (high 7.2)
- [CVE-2003-0936](https://insights.sbomify.com/CVE-2003-0936/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1970 and fix it if it is affected.

What it is: CVE-2005-1970 is a high-severity command injection vulnerability in n/a, published on 14 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-1970 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-2005-1970/ (Markdown: https://insights.sbomify.com/CVE-2005-1970/index.md)
```

## Sources

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

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