Bug 1275871 (CVE-2015-2695) - CVE-2015-2695 krb5: SPNEGO context aliasing bugs
Summary: CVE-2015-2695 krb5: SPNEGO context aliasing bugs
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2015-2695
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1275872
Blocks: 1275873
TreeView+ depends on / blocked
 
Reported: 2015-10-28 01:32 UTC by Kurt Seifried
Modified: 2019-09-29 13:39 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A resource-access flaw was discovered in krb5; the SPNEGO mechanism operates under an incorrect assumption when dealing with its context handles. If an application calls gss_inquire_context() on a partially-established SPNEGO context, an unauthenticated, remote attacker could possibly exploit this flaw by sending a specially crafted SPNEGO packet and crashing the system.
Clone Of:
Environment:
Last Closed: 2015-12-10 10:26:44 UTC


Attachments (Terms of Use)

Description Kurt Seifried 2015-10-28 01:32:52 UTC
The kerberos project reports:

The SPNEGO mechanism currently replaces its context handle with the
mechanism context handle upon establishment, under the assumption that
most GSS functions are only called after context establishment.  This
assumption is incorrect, and can lead to aliasing violations for some
programs.  Maintain the SPNEGO context structure after context
establishment and refer to it in all GSS methods.  Add initiate and
opened flags to the SPNEGO context structure for use in
gss_inquire_context() prior to context establishment.

CVE-2015-2695:

In MIT krb5 1.5 and later, applications which call
gss_inquire_context() on a partially-established SPNEGO context can
cause the GSS-API library to read from a pointer using the wrong type,
generally causing a process crash.  This bug may go unnoticed, because
the most common SPNEGO authentication scenario establishes the context
after just one call to gss_accept_sec_context().  Java server
applications using the native JGSS provider are vulnerable to this
bug.  A carefully crafted SPNEGO packet might allow the
gss_inquire_context() call to succeed with attacker-determined
results, but applications should not make access control decisions
based on gss_inquire_context() results prior to context establishment.

External References:
https://github.com/krb5/krb5/commit/b51b33f2bc5d1497ddf5bd107f791c101695000d

Comment 1 Kurt Seifried 2015-10-28 01:36:56 UTC
Created krb5 tracking bugs for this issue:

Affects: fedora-all [bug 1275872]


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