# CVE-2007-4191: Privilege escalation in n/a

> Local attackers can gain LocalSystem privileges by modifying service executables due to weak file permissions in the installation directory.

- **Severity:** Medium 6.9 (`AV:L/AC:M/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:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vq93-37v2-76p4

## What is CVE-2007-4191?

CVE-2007-4191 is a medium-severity vulnerability in n/a, published on 8 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Panda Antivirus 2008 stores service executables under the product's installation directory with weak permissions, which allows local users to obtain LocalSystem privileges by modifying PAVSRV51.EXE or other unspecified files, a related issue to CVE-2006-4657.

## Which versions are affected by CVE-2007-4191?

It affects 1 product.


Products: Panda Panda Antivirus.

## How do I fix CVE-2007-4191?

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

## Is CVE-2007-4191 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4191 exists.

Public exploit code:

- Panda AntiVirus 2008 - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3969](https://insights.sbomify.com/CVE-2007-3969/): Integer overflow in n/a (critical 9.3)
- [CVE-2000-0541](https://insights.sbomify.com/CVE-2000-0541/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4191 and fix it if it is affected.

What it is: CVE-2007-4191 is a medium-severity vulnerability in n/a, published on 8 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-4191 exists.

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-2007-4191/ (Markdown: https://insights.sbomify.com/CVE-2007-4191/index.md)
```

## Sources

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

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