# CVE-2014-3450: Privilege escalation in n/a

> Local attackers can escalate privileges in Panda Antivirus products via unspecified vectors, requiring an upgrade to secure the system.

- **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:** 23 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mhxp-j75h-h86w

## What is CVE-2014-3450?

CVE-2014-3450 is a high-severity vulnerability in n/a, published on 23 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in Panda Gold Protection and Global Protection 2014 7.01.01 and earlier, Internet Security 2014 19.01.01 and earlier, and AV Pro 2014 13.01.01 and earlier allows local users to gain privileges via unspecified vectors.

## Which versions are affected by CVE-2014-3450?

It affects 4 products.


Products: Pandasecurity Panda Av Pro 2014, Pandasecurity Panda Global Protection 2014, Pandasecurity Panda Gold Protection, Pandasecurity Panda Internet Security 2014.

## How do I fix CVE-2014-3450?

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

## Is CVE-2014-3450 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5307](https://insights.sbomify.com/CVE-2014-5307/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3450 and fix it if it is affected.

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

## Sources

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

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