# CVE-2006-3786: Privilege escalation in n/a

> Local attackers can modify caller ID files to escalate privileges to superuser in Symantec pcAnywhere.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f95j-vgvv-g77f

## What is CVE-2006-3786?

CVE-2006-3786 is a low-severity vulnerability in n/a, published on 21 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Symantec pcAnywhere 12.5 uses weak integrity protection for .cif (aka caller or CallerID) files, which allows local users to generate a custom .cif file and modify the superuser flag.

## Which versions are affected by CVE-2006-3786?

It affects 1 product.


Products: Symantec Pcanywhere.

## How do I fix CVE-2006-3786?

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

## Is CVE-2006-3786 being exploited?

There is no known exploitation of CVE-2006-3786 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-2005-1970](https://insights.sbomify.com/CVE-2005-1970/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-3786 and fix it if it is affected.

What it is: CVE-2006-3786 is a low-severity vulnerability in n/a, published on 21 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-3786 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-2006-3786/ (Markdown: https://insights.sbomify.com/CVE-2006-3786/index.md)
```

## Sources

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

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