First published: Thu Jul 19 2012(Updated: )
Multiple memory leaks in Performance Co-Pilot (PCP) before 3.6.5 allow remote attackers to cause a denial of service (memory consumption or daemon crash) via a large number of PDUs with (1) a crafted context number to the DoFetch function in pmcd/src/dofetch.c or (2) a negative type value to the __pmGetPDU function in libpcp/src/pdu.c.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Sgi Performance Co-pilot | <=3.6.4 | |
Sgi Performance Co-pilot | =2.1.1 | |
Sgi Performance Co-pilot | =2.1.2 | |
Sgi Performance Co-pilot | =2.1.3 | |
Sgi Performance Co-pilot | =2.1.4 | |
Sgi Performance Co-pilot | =2.1.5 | |
Sgi Performance Co-pilot | =2.1.6 | |
Sgi Performance Co-pilot | =2.1.7 | |
Sgi Performance Co-pilot | =2.1.8 | |
Sgi Performance Co-pilot | =2.1.9 | |
Sgi Performance Co-pilot | =2.1.10 | |
Sgi Performance Co-pilot | =2.1.11 | |
Sgi Performance Co-pilot | =2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-3420 is considered to have a high severity due to its potential to cause denial of service through memory leaks.
To fix CVE-2012-3420, upgrade to Performance Co-Pilot version 3.6.5 or later.
The potential impacts of CVE-2012-3420 include memory consumption and daemon crashes, leading to denial of service.
CVE-2012-3420 affects Performance Co-Pilot versions up to 3.6.4 and specific earlier versions such as 2.1.1 through 2.2.
Remote attackers can exploit CVE-2012-3420 by sending a large number of crafted PDUs to the vulnerable Performance Co-Pilot daemon.