# CVE-2009-4215: Privilege escalation in n/a

> Local attackers can escalate privileges by replacing executables due to weak file permissions in Panda Antivirus products.

- **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:** 7 Dec 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pwcw-cc5w-f5wp

## What is CVE-2009-4215?

CVE-2009-4215 is a high-severity vulnerability in n/a, published on 7 Dec 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Panda Global Protection 2010, Internet Security 2010, and Antivirus Pro 2010 use weak permissions (Everyone: Full Control) for the product files, which allows local users to gain privileges by replacing executables with Trojan horse programs.

Weakness: CWE-264

## Which versions are affected by CVE-2009-4215?

It affects 3 products.


Products: Pandasecurity Panda Antivirus, Pandasecurity Panda Global Protection, Pandasecurity Panda Internet Security.

## How do I fix CVE-2009-4215?

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

## Is CVE-2009-4215 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12042](https://insights.sbomify.com/CVE-2019-12042/): Privilege escalation in n/a (critical 9.8)
- [CVE-2008-5536](https://insights.sbomify.com/CVE-2008-5536/): Security feature bypass in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4215 and fix it if it is affected.

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

## Sources

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

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