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

> Local attackers can gain LocalSystem privileges by modifying service executables due to weak file permissions in Panda Internet Security.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 9 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vj34-f59j-c3g8

## What is CVE-2006-4657?

CVE-2006-4657 is a high-severity vulnerability in n/a, published on 9 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Panda Platinum Internet Security 2006 10.02.01 and 2007 11.00.00 stores service executables under the product's installation directory with weak permissions, which allows local users to obtain LocalSystem privileges by modifying (1) WebProxy.exe or (2) PAVSRV51.EXE.

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

It affects 1 product.


Products: Panda Panda Platinum Internet Security.

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

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

## Is CVE-2006-4657 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4658](https://insights.sbomify.com/CVE-2006-4658/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-4659](https://insights.sbomify.com/CVE-2006-4659/): Cross-site request forgery in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4657 is a high-severity vulnerability in n/a, published on 9 Sep 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-4657 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-4657/ (Markdown: https://insights.sbomify.com/CVE-2006-4657/index.md)
```

## Sources

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

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