LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1010179: PHKP including commit 88fd9cfdf14ea4b6ac3e3967feea7bcaabb6f03b is affected by: Improper Neutralization of S...

PHKP including commit 88fd9cfdf14ea4b6ac3e3967feea7bcaabb6f03b is affected by: Improper Neutralization of Special Elements used in a Command ('Command Injection'). The impact is: It is possible to manipulate gpg-keys or execute commands remotely. The component is: function pgp_exec() phkp.php:98. The attack vector is: HKP-Api: /pks/lookup?search.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

PHKP has a reported command injection weakness in its public key lookup handling. If an exposed PHKP service accepts crafted search input, an attacker may be able to alter GPG key material or run commands remotely. Public scoring and fixed-version information are not provided in the supplied sources.

Executive priority

Prioritize inventory and exposure reduction if PHKP is internet-facing. The potential impact is serious, but urgency cannot be fully scored from the supplied evidence because severity, fixed versions, and exploitation status are missing.

Technical view

The report identifies improper neutralization of command special elements in PHKP function pgp_exec() at phkp.php:98. The stated attack vector is the HKP API path /pks/lookup?search. Affected scope is PHKP including commit 88fd9cfdf14ea4b6ac3e3967feea7bcaabb6f03b as of 2018-09-15.

Likely exposure

Exposure is most likely where PHKP is deployed as an HKP keyserver or key lookup service, especially if /pks/lookup is internet-accessible. The supplied data provides no CPEs, package names, maintained release ranges, or downstream product mapping.

Exploitation context

The CVE states remote command execution or GPG key manipulation is possible through the lookup API. It is not listed as KEV, and the supplied sources do not state active exploitation, public exploit availability, or observed attacks.

Researcher notes

The record is sparse: no CVSS, CWE mapping, CPEs, or patch reference is included beyond the GitHub issue. Treat the endpoint and function names as primary triage anchors, and avoid broad conclusions about unrelated keyserver software.

Mitigation direction

  • Check the upstream PHKP issue and repository for fixed revisions or guidance.
  • Inventory PHKP deployments and compare code against the cited affected commit.
  • Restrict public access to /pks/lookup until exposure is understood.
  • Monitor for unexpected GPG key changes on affected systems.
  • Apply vendor or maintainer fixes when identified.

Validation and detection

  • Identify any running PHKP services and exposed HKP endpoints.
  • Confirm whether deployed code includes pgp_exec() behavior referenced by the CVE.
  • Review web logs for anomalous /pks/lookup search requests.
  • Check key material and service host logs for unexplained changes.
  • Document whether the exposed service matches the affected commit scope.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1010179 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PHKPPHKPincluding commit 88fd9cfdf14ea4b6ac3e3967feea7bcaabb6f03b (as of 2018-09-15)Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.