# 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. - **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Mar 2024 - **Updated:** 20 Nov 2025 - **Also known as:** ALSA-2024:2566, ALSA-2024:3264, AZL-110354, CLSA-2025-1764080949, DEBIAN-CVE-2024-3019, GHSA-g58w-wr93-q367, OESA-2024-1435, OESA-2024-1436, OESA-2024-1437, OESA-2024-1495, RHSA-2024:2566, RHSA-2024:3264, RHSA-2024:3321, RHSA-2024:3322, RHSA-2024:3323, RHSA-2024:3324, RHSA-2024:3325, RHSA-2024:3392, RLSA-2024:2566, RLSA-2024:3264, SUSE-SU-2025:03233-1, UBUNTU-CVE-2024-3019 ## 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 (Exposure of Resource to Wrong Sphere) ## Which versions are affected by CVE-2024-3019? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `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. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-3019 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2024-3019 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-3019/ (Markdown: https://insights.sbomify.com/CVE-2024-3019/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3019 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3019 - OSV: https://osv.dev/vulnerability/CVE-2024-3019 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-3019/ Summaries are generated and may contain mistakes; the official description above is the record.