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.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | RedHat | pcp-0:5.3.7-20.el8_10 | * |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | RedHat | pcp-0:5.0.2-8.el8_2 | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | pcp-0:5.2.5-7.el8_4 | * |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | RedHat | pcp-0:5.2.5-7.el8_4 | * |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | RedHat | pcp-0:5.2.5-7.el8_4 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | pcp-0:5.3.5-9.el8_6 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | pcp-0:5.3.7-18.el8_8 | * |
| Red Hat Enterprise Linux 9 | RedHat | pcp-0:6.2.0-2.el9_4 | * |
| Red Hat Enterprise Linux 9.0 Extended Update Support | RedHat | pcp-0:5.3.5-9.el9_0 | * |
| Red Hat Enterprise Linux 9.2 Extended Update Support | RedHat | pcp-0:6.0.1-6.el9_2 | * |
| Pcp | Ubuntu | mantic | * |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.