CVE-2024-3019 Pcp: exposure of the redis server backend allows remote command execution via pmproxy
Remote attackers can execute commands via pmproxy if the Redis backend is exposed, requiring manual service startup.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-3019?
CVE-2024-3019 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 28 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-668
Which versions are affected by CVE-2024-3019?
Linux distribution packages (40)
pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-conf AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-devel AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-doc AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2elasticsearch AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2graphite AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2influxdb AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2json AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2spark AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2xml AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-pcp2zabbix AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-export-zabbix-agent AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-gui AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-import-collectl2pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-import-ganglia2pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-import-iostat2pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-import-mrtg2pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-import-sar2pcp AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-libs AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-libs-devel AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-activemq AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-apache AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-bash AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-bcc AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-bind2 AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-bonding AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-bpftrace AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-cifs AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-cisco AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-dbping AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-denki AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-dm AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-docker AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-ds389 AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-ds389log AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-elasticsearch AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-gfs2 AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-gluster AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-gpfs AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
pcp-pmda-gpsd AlmaLinux:8 | All versions | 5.3.7-20.el8_10 |
How do I fix CVE-2024-3019?
Change a configuration setting.
Is CVE-2024-3019 being exploited?
There is no known exploitation of CVE-2024-3019 in the wild and no public exploit code.
Sources
Also known as ALSA-2024:2566, ALSA-2024:3264, AZL-110354, CLSA-2025-1764080949, DEBIAN-CVE-2024-3019, GHSA-g58w-wr93-q367 and 16 more.