public inbox for gentoo-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202405-11 ] MIT krb5: Multiple Vulnerabilities
Date: Sun, 05 May 2024 07:14:21 -0000	[thread overview]
Message-ID: <171489326149.8.611995914739645431@987c7955d8b1> (raw)

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202405-11
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: MIT krb5: Multiple Vulnerabilities
     Date: May 05, 2024
     Bugs: #803434, #809845, #879875, #917464
       ID: 202405-11

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

Multiple vulnerabilities have been discovered in MIT krb5, the worst of
which could lead to remote code execution.

Background
==========

MIT krb5 is the free implementation of the Kerberos network
authentication protocol by the Massachusetts Institute of Technology.

Affected packages
=================

Package             Vulnerable    Unaffected
------------------  ------------  ------------
app-crypt/mit-krb5  < 1.21.2      >= 1.21.2

Description
===========

Multiple vulnerabilities have been discovered in MIT krb5. Please review
the CVE identifiers referenced below for details.

Impact
======

Please review the referenced CVE identifiers for details.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All MIT krb5 users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=app-crypt/mit-krb5-1.21.2"

References
==========

[ 1 ] CVE-2021-36222
      https://nvd.nist.gov/vuln/detail/CVE-2021-36222
[ 2 ] CVE-2021-37750
      https://nvd.nist.gov/vuln/detail/CVE-2021-37750
[ 3 ] CVE-2022-42898
      https://nvd.nist.gov/vuln/detail/CVE-2022-42898
[ 4 ] CVE-2023-36054
      https://nvd.nist.gov/vuln/detail/CVE-2023-36054
[ 5 ] CVE-2023-39975
      https://nvd.nist.gov/vuln/detail/CVE-2023-39975

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202405-11

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2024 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2024-05-05  7:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171489326149.8.611995914739645431@987c7955d8b1 \
    --to=glsamaker@gentoo.org \
    --cc=gentoo-announce@lists.gentoo.org \
    --cc=security@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox