{"id":"CVE-2024-3019","title":"Pcp: exposure of the redis server backend allows remote command execution via pmproxy","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 r…","severity":"high","cvss":8.8,"cvssVector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cvssSource":"cna","cwe":["CWE-668"],"vendor":"Red Hat","product":"pcp","affected":["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)","pcp","pcp","pcp"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2024-04-25T19:20:31.653267Z"},"published":"2024-03-28","updated":"2026-11-04","sourceUpdated":"2026-11-04T21:11:33.114Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-3019","references":[{"url":"https://access.redhat.com/errata/RHSA-2024:2566","label":"RHSA-2024:2566"},{"url":"https://access.redhat.com/errata/RHSA-2024:3264","label":"RHSA-2024:3264"},{"url":"https://access.redhat.com/errata/RHSA-2024:3321","label":"RHSA-2024:3321"},{"url":"https://access.redhat.com/errata/RHSA-2024:3322","label":"RHSA-2024:3322"},{"url":"https://access.redhat.com/errata/RHSA-2024:3323","label":"RHSA-2024:3323"},{"url":"https://access.redhat.com/errata/RHSA-2024:3324","label":"RHSA-2024:3324"},{"url":"https://access.redhat.com/errata/RHSA-2024:3325","label":"RHSA-2024:3325"},{"url":"https://access.redhat.com/errata/RHSA-2024:3392","label":"RHSA-2024:3392"},{"url":"https://access.redhat.com/security/cve/CVE-2024-3019"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2271898","label":"RHBZ#2271898"}],"tags":["cve.org"],"epss":0.01067,"epssPercentile":0.64875,"ingestedAt":"2026-11-05T21:36:00.601Z","slug":"CVE-2024-3019","body":"## Overview\n\nA 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.\n\n## Affected\n\n- `pcp >= 4.3.4 < *`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp (all versions)`\n- `pcp`\n- `pcp`\n- `pcp`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n### Workarounds\n\nTo mitigate this flaw, stop and disable the pmproxy.service or disable the Redis server backend via the pmproxy configuration file.\n\nTo stop and disable the pmproxy.service, run the following command:\n~~~\n# systemctl disable --now pmproxy.service\n~~~\n\nTo disable the Redis backend server via the pmproxy configuration file:\n~~~\n# sed -i 's/redis.enabled = true/redis.enabled = false/g' /etc/pcp/pmproxy/pmproxy.conf\n# systemctl restart pmproxy.service\n~~~","depth":"twilight","depthScore":49,"depthScoreParts":{"impact":48.4,"likelihood":0.2,"exploitation":0,"ransomware":0},"changes":[]}