# CVE-2018-1000885: Command injection in n/a

> Attackers can execute arbitrary commands remotely via the HKP API search parameter in the PHKP library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-ch67-4785-wgf3

## What is CVE-2018-1000885?

CVE-2018-1000885 is a critical command injection vulnerability in n/a, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHKP version including commit 88fd9cfdf14ea4b6ac3e3967feea7bcaabb6f03b contains a Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in function pgp_exec() phkp.php:98 that can result in It is possible to manipulate gpg-keys or execute commands remotely. This attack appear to be exploitable via HKP-Api: /pks/lookup?search.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-1000885?

It affects 1 product.


Products: Phkp Project Phkp.

## How do I fix CVE-2018-1000885?

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

## Is CVE-2018-1000885 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-1010179](https://insights.sbomify.com/CVE-2019-1010179/): Command injection in PHKP (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000885 and fix it if it is affected.

What it is: CVE-2018-1000885 is a critical command injection vulnerability in n/a, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000885 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-2018-1000885/ (Markdown: https://insights.sbomify.com/CVE-2018-1000885/index.md)
```

## Sources

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

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