Pcp: exposure of the redis server backend allows remote command execution via pmproxy
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in PCP. The default pmproxy configuration exposes the Redis server backend to the local network, allowing remote command execution with the privileges of the Redis user. This issue can only be exploited when pmproxy is running. By default, pmproxy is not running and needs to be started manually. The pmproxy service is usually started from the 'Metrics settings' page of the Cockpit web interface. This flaw affects PCP versions 4.3.4 and newer.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- pcp
From 4.3.4
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported
- pcp
Version range not reported