Bug 426568 (CVE-2007-5360)

Summary: CVE-2007-5360 tog-pegasus pam authentication buffer overflow
Product: [Other] Security Response Reporter: Mark J. Cox <mjc>
Component: vulnerabilityAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED NOTABUG QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: fenlason, nalin, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-08 08:44:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mark J. Cox 2007-12-22 08:32:49 UTC
VMWare reported a buffer overflow vulnerability in the PAM authentication code
in the OpenPegasus CIM management server. This vulnerability can be exploited
remotely and results in arbitrary code execution with the privileges of the
cimserver process.

Details in next comment.

Due to the nature of the bug, and the Red Hat changes to tog-pegasus package,
it's quite likely it has a much reduced impact, this will have to be investigated.

Current embargo is Dec 27th.  I've asked for an extension to Jan 3rd at the

Comment 2 Mark J. Cox 2007-12-22 08:35:04 UTC
There were some changes made to authentication code for Red Hat version, these
need to be checked

The sprintf is unfortunately not caught by fortify_source (because it's C++)

We do ship with a SELinux policy by default (it was a requirement of shipping
this package)

Comment 3 Mark J. Cox 2007-12-22 12:37:54 UTC
Not vulnerable.  The RHEL4 and RHEL5 builds of tog-pegasus do not build with
PEGASUS_USE_PAM_STANDALONE_PROC and therefore do not compile the vulnerable

Comment 6 Tomas Hoger 2008-01-08 07:41:14 UTC
Public now:


Comment 7 Mark J. Cox 2008-01-08 08:44:35 UTC
Whilst this issue does not affect Red Hat Enterprise Linux tog-pegasus packages,
we found a similar issue that does.  Please see