Remote code execution via enabled Redis proxying
Published Mar 28, 2024 · Updated Nov 20, 2025
Exposure of the Redis backend in Performance Co-Pilot 4.3.4 and newer allows remote attackers to execute commands through pmproxy. The default src/pmproxy/pmproxy.conf sets redis.enabled to true, letting pmproxy forward arbitrary RESP commands to a Redis server that otherwise restricts connections. Exploitation requires pmproxy to be running, typically after activation through Cockpit Metrics, and executes with the Redis user's privileges.
Summary
What happened
Exposure of the Redis backend in Performance Co-Pilot 4.3.4 and newer allows remote attackers to execute commands through pmproxy. The default src/pmproxy/pmproxy.conf sets redis.enabled to true, letting pmproxy forward arbitrary RESP commands to a Redis server that otherwise restricts connections. Exploitation requires pmproxy to be running, typically after activation through Cockpit Metrics, and executes with the Redis user's privileges.
The record
- CVE
- CVE-2024-3019
- Published
- Mar 28, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
- Classifications
- CWE-668, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo