CVE-2024-3019

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 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.

Affected Software

VendorProductVersion RangeStatus
4.3.4 < *affected
Red HatRed Hat Enterprise Linux 80:5.3.7-20.el8_10 < *unaffected
Red HatRed Hat Enterprise Linux 8.2 Advanced Update Support0:5.0.2-8.el8_2 < *unaffected
Red HatRed Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support0:5.2.5-7.el8_4 < *unaffected
Red HatRed Hat Enterprise Linux 8.4 Telecommunications Update Service0:5.2.5-7.el8_4 < *unaffected
Red HatRed Hat Enterprise Linux 8.4 Update Services for SAP Solutions0:5.2.5-7.el8_4 < *unaffected
Red HatRed Hat Enterprise Linux 8.6 Extended Update Support0:5.3.5-9.el8_6 < *unaffected
Red HatRed Hat Enterprise Linux 8.8 Extended Update Support0:5.3.7-18.el8_8 < *unaffected
Red HatRed Hat Enterprise Linux 90:6.2.0-2.el9_4 < *unaffected
Red HatRed Hat Enterprise Linux 9.0 Extended Update Support0:5.3.5-9.el9_0 < *unaffected
Red HatRed Hat Enterprise Linux 9.2 Extended Update Support0:6.0.1-6.el9_2 < *unaffected

Weaknesses

  • CWE-668: Exposure of Resource to Wrong Sphere

Workarounds

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 &#39;s/redis.enabled = true/redis.enabled = false/g&#39; /etc/pcp/pmproxy/pmproxy.conf
# systemctl restart pmproxy.service

ADP Enrichment

CISA ADP Vulnrichment

  • SSVC:
  • Exploitation: none
    • Automatable: no
    • Technical Impact: total

CVE Program Container

Additional References

References