Bug 675254 - (CVE-2011-0539) CVE-2011-0539 OpenSSH: legacy certificate generation information leak
CVE-2011-0539 OpenSSH: legacy certificate generation information leak
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 718133
  Show dependency treegraph
Reported: 2011-02-04 12:59 EST by Josh Bressers
Modified: 2011-07-01 10:13 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-07-01 10:13:25 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 Josh Bressers 2011-02-04 12:59:20 EST
From the upstream advisory:

        When generating legacy *-cert-v00@openssh.com certificates,
        the nonce field was not being correctly filled with random
        data but was left uninitialised, containing the contents of
        the stack.

        The contents of the stack at this point in ssh-keygen's
        execution do not appear to leak the CA private key or other
        sensitive data, but this possibility cannot be excluded on
        all platforms and library versions.

        If certificates are generated using user-specified contents
        (as opposed to the CA specifying all fields) then they will
        be less resistant to hash collision attacks. Fortunately,
        such attacks are not currently considered practical for the
        SHA family of hashes used to sign these certificates.

This only affected OpenSSH versions 5.6 and 5.7, which Red Hat does not
currently ship.
Comment 1 Tomas Hoger 2011-07-01 03:01:38 EDT
Created openssh tracking bugs for this issue

Affects: fedora-15 [bug 718133]
Comment 2 Tomas Hoger 2011-07-01 10:13:25 EDT

Not vulnerable. This issue did not affect the versions of openssh as shipped with Red Hat Enterprise Linux 4, 5, or 6.

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