krb5 was updated to fix five security issues.

These security issues were fixed :

  - CVE-2014-5351: current keys returned when randomizing     the keys for a service principal (bnc#897874) 

  - CVE-2014-5352: An authenticated attacker could cause a     vulnerable application (including kadmind) to crash or     to execute arbitrary code (bnc#912002).

  - CVE-2014-9421: An authenticated attacker could cause     kadmind or other vulnerable server application to crash     or to execute arbitrary code (bnc#912002).

  - CVE-2014-9422: An attacker who possess the key of a     particularly named principal (such as 'kad/root') could     impersonate any user to kadmind and perform     administrative actions as that user (bnc#912002).

  - CVE-2014-9423: An attacker could attempt to glean     sensitive information from the four or eight bytes of     uninitialized data output by kadmind or other libgssrpc     server application. Because MIT krb5 generally sanitizes     memory containing krb5 keys before freeing it, it is     unlikely that kadmind would leak Kerberos key     information, but it is not impossible (bnc#912002).

This non-security issue was fixed :

  - Work around replay cache creation race (bnc#898439).

Multiples vulnerabilities have been found in krb5, the MIT implementation of Kerberos :

CVE-2014-5352

Incorrect memory management in the libgssapi_krb5 library might result in denial of service or the execution of arbitrary code.

CVE-2014-9421

Incorrect memory management in kadmind's processing of XDR data might result in denial of service or the execution of arbitrary code.

CVE-2014-9422

Incorrect processing of two-component server principals might result in impersonation attacks.

CVE-2014-9423

An information leak in the libgssrpc library.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Multiple vulnerabilities has been discovered and corrected in krb5 :

The krb5_gss_process_context_token function in lib/gssapi/krb5/process_context_token.c in the libgssapi_krb5 library in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly maintain security-context handles, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and daemon crash) or possibly execute arbitrary code via crafted GSSAPI traffic, as demonstrated by traffic to kadmind (CVE-2014-5352).

MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-bounds read) by omitting the '\0' character, related to appl/user_user/server.c and lib/krb5/krb/recvauth.c (CVE-2014-5355).

The auth_gssapi_unwrap_data function in lib/rpc/auth_gssapi_misc.c in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly handle partial XDR deserialization, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and daemon crash) or possibly execute arbitrary code via malformed XDR data, as demonstrated by data sent to kadmind (CVE-2014-9421).

The check_rpcsec_auth function in kadmin/server/kadm_rpc_svc.c in kadmind in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 allows remote authenticated users to bypass a kadmin/* authorization check and obtain administrative access by leveraging access to a two-component principal with an initial kadmind substring, as demonstrated by a ka/x principal (CVE-2014-9422).

The svcauth_gss_accept_sec_context function in lib/rpc/svc_auth_gss.c in MIT Kerberos 5 (aka krb5) 1.11.x through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 transmits uninitialized interposer data to clients, which allows remote attackers to obtain sensitive information from process heap memory by sniffing the network for data in a handle field (CVE-2014-9423).

The updated packages provides a solution for these security issues.

Updated krb5 packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Kerberos is a networked authentication system which allows clients and servers to authenticate to each other with the help of a trusted third party, the Kerberos KDC.

The following security issues are fixed with this release :

A use-after-free flaw was found in the way the MIT Kerberos libgssapi_krb5 library processed valid context deletion tokens. An attacker able to make an application using the GSS-API library (libgssapi) could call the gss_process_context_token() function and use this flaw to crash that application. (CVE-2014-5352)

If kadmind were used with an LDAP back end for the KDC database, a remote, authenticated attacker who has the permissions to set the password policy could crash kadmind by attempting to use a named ticket policy object as a password policy for a principal.
(CVE-2014-5353)

It was found that the krb5_read_message() function of MIT Kerberos did not correctly sanitize input, and could create invalid krb5_data objects. A remote, unauthenticated attacker could use this flaw to crash a Kerberos child process via a specially crafted request.
(CVE-2014-5355)

A double-free flaw was found in the way MIT Kerberos handled invalid External Data Representation (XDR) data. An authenticated user could use this flaw to crash the MIT Kerberos administration server (kadmind), or other applications using Kerberos libraries, via specially crafted XDR packets. (CVE-2014-9421)

It was found that the MIT Kerberos administration server (kadmind) incorrectly accepted certain authentication requests for two-component server principal names. A remote attacker able to acquire a key with a particularly named principal (such as 'kad/x') could use this flaw to impersonate any user to kadmind, and perform administrative actions as that user. (CVE-2014-9422)

Red Hat would like to thank the MIT Kerberos project for reporting CVE-2014-5352, CVE-2014-9421, and CVE-2014-9422. The MIT Kerberos project acknowledges Nico Williams for assisting with the analysis of CVE-2014-5352.

All krb5 users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

The following security issues are fixed with this release :

A use-after-free flaw was found in the way the MIT Kerberos libgssapi_krb5 library processed valid context deletion tokens. An attacker able to make an application using the GSS-API library (libgssapi) could call the gss_process_context_token() function and use this flaw to crash that application. (CVE-2014-5352)

If kadmind were used with an LDAP back end for the KDC database, a remote, authenticated attacker who has the permissions to set the password policy could crash kadmind by attempting to use a named ticket policy object as a password policy for a principal.
(CVE-2014-5353)

It was found that the krb5_read_message() function of MIT Kerberos did not correctly sanitize input, and could create invalid krb5_data objects. A remote, unauthenticated attacker could use this flaw to crash a Kerberos child process via a specially crafted request.
(CVE-2014-5355)

A double-free flaw was found in the way MIT Kerberos handled invalid External Data Representation (XDR) data. An authenticated user could use this flaw to crash the MIT Kerberos administration server (kadmind), or other applications using Kerberos libraries, via specially crafted XDR packets. (CVE-2014-9421)

It was found that the MIT Kerberos administration server (kadmind) incorrectly accepted certain authentication requests for two-component server principal names. A remote attacker able to acquire a key with a particularly named principal (such as 'kad/x') could use this flaw to impersonate any user to kadmind, and perform administrative actions as that user. (CVE-2014-9422)

MIT kerberos krb5 was updated to fix several security issues and bugs.

Security issues fixed: CVE-2014-5351: The kadm5_randkey_principal_3 function in lib/kadm5/srv/svr_principal.c in kadmind in MIT Kerberos 5 (aka krb5) sent old keys in a response to a -randkey -keepold request, which allowed remote authenticated users to forge tickets by leveraging administrative access.

  - CVE-2014-5352: In the MIT krb5 libgssapi_krb5 library,     after gss_process_context_token() is used to process a     valid context deletion token, the caller was left with a     security context handle containing a dangling pointer.
    Further uses of this handle would have resulted in     use-after-free and double-free memory access violations.
    libgssrpc server applications such as kadmind were     vulnerable as they can be instructed to call     gss_process_context_token().

  - CVE-2014-9421: If the MIT krb5 kadmind daemon receives     invalid XDR data from an authenticated user, it may have     performed use-after-free and double-free memory access     violations while cleaning up the partial deserialization     results. Other libgssrpc server applications might also     been vulnerable if they contain insufficiently defensive     XDR functions.

  - CVE-2014-9422: The MIT krb5 kadmind daemon incorrectly     accepted authentications to two-component server     principals whose first component is a left substring of     'kadmin' or whose realm is a left prefix of the default     realm.

  - CVE-2014-9423: libgssrpc applications including kadmind     output four or eight bytes of uninitialized memory to     the network as part of an unused 'handle' field in     replies to clients.

Bugs fixed :

  - Work around replay cache creation race; (bnc#898439).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	名稱	產品	系列	已發布	已更新	嚴重性
81304	openSUSE Security Update : krb5 (openSUSE-2015-128)	Nessus	SuSE Local Security Checks	2015/2/12	2021/1/19	high
82129	Debian DLA-146-1 : krb5 security update	Nessus	Debian Local Security Checks	2015/3/26	2021/1/11	high
82322	Mandriva Linux Security Advisory : krb5 (MDVSA-2015:069)	Nessus	Mandriva Local Security Checks	2015/3/30	2021/1/6	high
82656	RHEL 6 : krb5 (RHSA-2015:0794)	Nessus	Red Hat Local Security Checks	2015/4/9	2021/2/5	high
82694	Scientific Linux Security Update : krb5 on SL6.x i386/x86_64 (20150409)	Nessus	Scientific Linux Local Security Checks	2015/4/10	2021/1/14	high
83682	SUSE SLES12 Security Update : krb5 (SUSE-SU-2015:0290-1)	Nessus	SuSE Local Security Checks	2015/5/20	2021/1/6	high

偵測

搜尋 Plugin

high

high

high

high

high

high