# CVE-2000-0264: Security feature bypass in n/a

> Local users can bypass registry editing restrictions in Panda Security to modify the registry and escalate privileges.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2322-3mhq-32v4

## What is CVE-2000-0264?

CVE-2000-0264 is a low-severity vulnerability in n/a, published on 12 Jul 2000. 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

Panda Security 3.0 with registry editing disabled allows users to edit the registry and gain privileges by directly executing a .reg file or using other methods.

## Which versions are affected by CVE-2000-0264?

It affects 1 product.


Products: Panda Panda Security.

## How do I fix CVE-2000-0264?

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

## Is CVE-2000-0264 being exploited?

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

Public exploit code:

- Panda Security 3.0 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0265](https://insights.sbomify.com/CVE-2000-0265/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0264 and fix it if it is affected.

What it is: CVE-2000-0264 is a low-severity vulnerability in n/a, published on 12 Jul 2000. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0264 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-2000-0264/ (Markdown: https://insights.sbomify.com/CVE-2000-0264/index.md)
```

## Sources

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

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