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

> Authenticated users can escalate privileges and execute arbitrary code via malicious data objects sent to PGP Desktop named pipes.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/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:** 30 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j6pr-2432-gprv

## What is CVE-2007-0603?

CVE-2007-0603 is a high-severity vulnerability in n/a, published on 30 Jan 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PGP Desktop before 9.5.1 does not validate data objects received over the (1) \pipe\pgpserv named pipe for PGPServ.exe or the (2) \pipe\pgpsdkserv named pipe for PGPsdkServ.exe, which allows remote authenticated users to gain privileges by sending a data object representing an absolute pointer, which causes code execution at the corresponding address.

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

It affects 1 product.


Products: Pgp Corporate Desktop.

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

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

## Is CVE-2007-0603 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0850](https://insights.sbomify.com/CVE-2002-0850/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1016](https://insights.sbomify.com/CVE-2001-1016/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-0788](https://insights.sbomify.com/CVE-2002-0788/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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