Bug 208347 - (CVE-2006-5051) CVE-2006-5051 unsafe GSSAPI signal handler
CVE-2006-5051 unsafe GSSAPI signal handler
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openssh (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Brian Brock
: Security
Depends On:
  Show dependency treegraph
Reported: 2006-09-27 18:41 EDT by Mark J. Cox (Product Security)
Modified: 2012-09-20 15:38 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2006-0697
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-28 20:18:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2006-09-27 18:41:06 EDT
OpenSSH 4.4 was released and mentions:

        * Fix an unsafe signal hander reported by Mark Dowd. The
        signal handler was vulnerable to a race condition that could
        be exploited to perform a pre-authentication denial of
        service. On portable OpenSSH, this vulnerability could
        theoretically lead to pre-authentication remote code execution
        if GSSAPI authentication is enabled, but the likelihood of
        successful exploitation appears remote.

This could only affect RHEL4 as previous RHEL did not support GSSAPI
Comment 2 Josh Bressers 2006-09-28 11:17:17 EDT
I've done some analysis of this issue and received a mail from Mark Dowd
regarding this vulnerability.  The upstream details are misleading.

The problem is that the signal handling in openssh does quite a lot and can
introduce a race condition during cleanup.  This flaw could possibly cause a
double free condition within the kerberos cleanup code.  The GSSAPI code is
completely harmless, upstream calling this issue a GSSAPI issue leads me to
believe they did not analyze, nor try to understand this issue.

There is also PAM cleanup code which is executed.  This PAM source hasn't been
investigated so the possible outcome is currently unknown.

Red Hat will be fixing this issue due to the incredible complexity and possible
danger.  This is a case of better safe than sorry.
Comment 3 Josh Bressers 2006-09-28 11:22:36 EDT
This issue also likely affects RHEL3
Comment 5 Red Hat Bugzilla 2006-09-28 20:18:27 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.