CVE-2012-5530: Low severity performance co-pilot vulnerability
A security flaw was found in the way Performance Co-Pilot (PCP), a framework and services to support system-level performance monitoring and performance management, performed management of its temporary files used by various services from the suite. A local attacker could use this flaw to conduct symbolic link attacks (alter or remove different system files, accessible with the privileges of the user running the PCP suite, than it was originally intended).
References: [1] https://bugzilla.novell.com/showbug.cgi?id=782967 (private)
Other sources
The (1) pcmd and (2) pmlogger init scripts in Performance Co-Pilot (PCP) before 3.6.10 allow local users to overwrite arbitrary files via a symlink attack on a /var/tmp/##### temporary file.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2012-5530?
CVE-2012-5530 is classified as a medium severity vulnerability.
How do I fix CVE-2012-5530?
To fix CVE-2012-5530, you should upgrade to Performance Co-Pilot version 3.6.10 or later.
What causes CVE-2012-5530?
CVE-2012-5530 is caused by improper management of temporary files in Performance Co-Pilot.
Who is affected by CVE-2012-5530?
CVE-2012-5530 affects all versions of Performance Co-Pilot up to 3.6.9 and specific versions like 2.1.1 to 2.2.
Can CVE-2012-5530 be exploited remotely?
No, CVE-2012-5530 requires local access for exploitation.