CVE-2024-45770

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.

PCP provides a range of services that may be used to monitor and manage system performance. These services are distributed and scalable to accommodate the most complex system configurations and performance problems.

Security Fix(es):

A vulnerability was found in Performance Co-Pilot (PCP).  This flaw allows an attacker to send specially crafted data to the system, which could cause the program to misbehave or crash.(CVE-2024-45769)

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.(CVE-2024-45770)

PCP provides a range of services that may be used to monitor and manage system performance. These services are distributed and scalable to accommodate the most complex system configurations and performance problems.

Security Fix(es):

A vulnerability was found in Performance Co-Pilot (PCP).  This flaw allows an attacker to send specially crafted data to the system, which could cause the program to misbehave or crash.(CVE-2024-45769)

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.(CVE-2024-45770)

PCP provides a range of services that may be used to monitor and manage system performance. These services are distributed and scalable to accommodate the most complex system configurations and performance problems.

Security Fix(es):

A vulnerability was found in Performance Co-Pilot (PCP).  This flaw allows an attacker to send specially crafted data to the system, which could cause the program to misbehave or crash.(CVE-2024-45769)

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.(CVE-2024-45770)

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)
• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)
• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)
• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

• CVE-2024-45770: guard pmpost against symlink attacks on $PCP_LOG_DIR/NOTICES
• CVE-2024-45769: harden libpcp __pmDecodeValueSet to prevent heap corruption from crafted PDUs

A vulnerability was found in Performance Co-Pilot (PCP). This flaw can only be exploited if an attacker has access to a compromised PCP system account. The issue is related to the pmpost tool, which is used to log messages in the system. Under certain conditions, it runs with high-level privileges.

These are all security issues fixed in the libpcp-devel-6.3.8-1.1 package on the GA media of openSUSE Tumbleweed.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)

• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)

• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight distributed architecture makes it particularly well-suited to centralized analysis of complex systems.

Security Fix(es):

• pcp: pmpost symlink attack allows escalating pcp to root user (CVE-2024-45770)

• pcp: pmcd heap corruption through metric pmstore operations (CVE-2024-45769)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

This update for pcp fixes the following issues:

pcp was updated from version 5.3.7 to version 6.2.0 (jsc#PED-8192, jsc#PED-8389):

• Security issues fixed:

  • CVE-2024-45770: Fixed a symlink attack that allows escalating from the pcp to the root user (bsc#1230552)
  • CVE-2024-45769: Fixed a heap corruption through metric pmstore operations (bsc#1230551)
  • CVE-2023-6917: Fixed local privilege escalation from pcp user to root in /usr/libexec/pcp/lib/pmproxy (bsc#1217826)
  • CVE-2024-3019: Disabled redis proxy by default (bsc#1222121)

• Major changes:

  • Add version 3 PCP archive support: instance domain change-deltas, Y2038-safe timestamps, nanosecond-precision timestamps, arbitrary timezones support, 64-bit file offsets used throughout for larger (beyond 2GB) individual volumes.
    • Opt-in using the /etc/pcp.conf PCP_ARCHIVE_VERSION setting
    • Version 2 archives remain the default (for next few years).
  • Switch to using OpenSSL only throughout PCP (dropped NSS/NSPR); this impacts on libpcp, PMAPI clients and PMCD use of encryption; these are now configured and used consistently with pmproxy HTTPS support and redis-server, which were both already using OpenSSL.
  • New nanosecond precision timestamp PMAPI calls for PCP library interfaces that make use of timestamps.
    These are all optional, and full backward compatibility is preserved for existing tools.
  • For the full list of changes please consult the packaged CHANGELOG file

• Other packaging changes:

  • Moved pmlogger_daily into main package (bsc#1222815)
  • Change dependency from openssl-devel >= 1.1.1 to openssl-devel >= 1.0.2p. Required for SLE-12.
  • Introduce 'pmda-resctrl' package, disabled for architectures other than x86_64.
  • Change the architecture for various subpackages to 'noarch' as they contain no binaries.
  • Disable 'pmda-mssql', as it fails to build.

This update for pcp fixes the following issues:

pcp was updated from version 5.2.5 to version 6.2.0 (jsc#PED-8192, jsc#PED-8389):

• Security issues fixed:

  • CVE-2024-45770: Fixed a symlink attack that allows escalating from the pcp to the root user (bsc#1230552)
  • CVE-2024-45769: Fixed a heap corruption through metric pmstore operations (bsc#1230551)
  • CVE-2023-6917: Fixed local privilege escalation from pcp user to root in /usr/libexec/pcp/lib/pmproxy (bsc#1217826)

• Major changes:

  • Add version 3 PCP archive support: instance domain change-deltas, Y2038-safe timestamps, nanosecond-precision timestamps, arbitrary timezones support, 64-bit file offsets used throughout for larger (beyond 2GB) individual volumes
    • Opt-in using the /etc/pcp.conf PCP_ARCHIVE_VERSION setting
    • Version 2 archives remain the default (for next few years)
  • Switch to using OpenSSL only throughout PCP (dropped NSS/NSPR); this impacts on libpcp, PMAPI clients and PMCD use of encryption; these are now configured and used consistently with pmproxy HTTPS support and redis-server, which were both already using OpenSSL.
  • New nanosecond precision timestamp PMAPI calls for PCP library interfaces that make use of timestamps These are all optional, and full backward compatibility is preserved for existing tools.
  • For the full list of changes please consult the packaged CHANGELOG file

• Other packaging changes:

  • Moved pmlogger_daily into the main package (bsc#1222815)
  • Change dependency from openssl-devel >= 1.1.1 to openssl-devel >= 1.0.2p. Required for SLE-12
  • Introduce 'pmda-resctrl' package, disabled for architectures other than x86_64
  • Change the architecture for various subpackages to 'noarch' as they contain no binaries
  • Disable 'pmda-mssql', as it fails to build

This update for pcp fixes the following issues:

pcp was updated from version 3.11.9 to version 6.2.0 (jsc#PED-8192, jsc#PED-8389):

• Security issues fixed:

  • CVE-2024-45770: Fixed a symlink attack that allows escalating from the pcp to the root user (bsc#1230552)
  • CVE-2024-45769: Fixed a heap corruption through metric pmstore operations (bsc#1230551)
  • CVE-2023-6917: Fixed local privilege escalation from pcp user to root in /usr/libexec/pcp/lib/pmproxy (bsc#1217826)
  • CVE-2024-3019: Disabled redis proxy by default (bsc#1222121)

• Major changes:

  • Add version 3 PCP archive support: instance domain change-deltas, Y2038-safe timestamps, nanosecond-precision timestamps, arbitrary timezones support, 64-bit file offsets used throughout for larger (beyond 2GB) individual volumes.
    • Opt-in using the /etc/pcp.conf PCP_ARCHIVE_VERSION setting
    • Version 2 archives remain the default (for next few years).
  • Switch to using OpenSSL only throughout PCP (dropped NSS/NSPR); this impacts on libpcp, PMAPI clients and PMCD use of encryption; these are now configured and used consistently with pmproxy HTTPS support and redis-server, which were both already using OpenSSL.
  • New nanosecond precision timestamp PMAPI calls for PCP library interfaces that make use of timestamps.
    These are all optional, and full backward compatibility is preserved for existing tools.
  • For the full list of changes please consult the packaged CHANGELOG file

• Other packaging changes:

  • Reintroduce libuv support for SUSE Linux Enterprise 15 (bsc#1231345)
  • Moved pmlogger_daily into main package (bsc#1222815)
  • Switched logutil and pmieutil scripts from Type=oneshot to Type=exec (bsc#1186511)
  • Change dependency from openssl-devel >= 1.1.1 to openssl-devel >= 1.0.2p. Required for SUSE Linux Enterprise 12.
  • Disabled 'pmda-infiniband' subpackage for SUSE Linux Enterprise 12 to resolve build issues.
  • Introduce 'pmda-resctrl' package, disabled for architectures other than x86_64.
  • Change the architecture for various subpackages to 'noarch' as they contain no binaries.
  • Disable 'pmda-mssql', as it fails to build.

This update for pcp fixes the following issues:

Upgrade to 6.2.0 (bsc#1217826 / PED#8192):

• CVE-2024-45770: Fixed symlink race (bsc#1230552).
• CVE-2024-45769: Fixed pmstore corruption (bsc#1230551)
• CVE-2023-6917: Fixed local privilege escalation from pcp user to root (bsc#1217826).

Bug fixes:

• Reintroduce libuv support for SLE >= 15 (bsc#1231345).
• move pmlogger_daily into main package (bsc#1222815)

This update for pcp fixes the following issues:

• CVE-2024-45770: Fixed pmpost symlink attack allowing escalating pcp to root user (bsc#1230552).
• CVE-2024-45769: Fixed pmcd heap corruption through metric pmstore operations (bsc#1230551).
• CVE-2024-3019: Fixed exposure of the redis backend server allowing remote command execution via pmproxy (bsc#1222121).
• CVE-2023-6917: Fixed Local privilege escalation from pcp user to root in /usr/libexec/pcp/lib/pmproxy (bsc#1217826).

Other fixes:

• Updated to version 6.2.0

This update for pcp fixes the following issues:

• CVE-2024-45769: Fixed pmcd heap corruption through metric pmstore operations (bsc#1230551).
• CVE-2024-45770: Fixed pmpost symlink attack allowing escalating pcp to root user (bsc#1230552).