CVE-2024-3019High· 8.8▾ TwilightA 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 r…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
1.1%
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.
pcp >= 4.3.4 < *pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcp (all versions)pcppcppcpRefer to the linked advisories for vendor-supplied fixes and affected version ranges.
To mitigate this flaw, stop and disable the pmproxy.service or disable the Redis server backend via the pmproxy configuration file.
To stop and disable the pmproxy.service, run the following command:
# systemctl disable --now pmproxy.service
To disable the Redis backend server via the pmproxy configuration file:
# sed -i 's/redis.enabled = true/redis.enabled = false/g' /etc/pcp/pmproxy/pmproxy.conf
# systemctl restart pmproxy.service
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-16530Medium· 6.5Pcp: pcp: remote denial of service and information leakage
CVE-2026-16531Medium· 5.3Pcp: pcp: arbitrary file creation via path traversal in pmproxy logger servlet
CVE-2024-45770Medium· 4.4Pcp: pmpost symlink attack allows escalating pcp to root user
CVE-2024-45769Medium· 5.5Pcp: pmcd heap corruption through metric pmstore operations
CVE-2023-6917Medium· 6.0Pcp: unsafe use of directories allows pcp to root privilege escalation
CVE-2026-16524High· 7.8A command injection flaw in PCP's linux_sockets PMDA allows malicious shell metacharacters via the network.persocket.filter metric. This failed validation lets attackers execute arbitrary commands as the PMDA user when metrics refresh.