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 202311-05 ] LinuxCIFS utils: Multiple Vulnerabilities
Date: Fri, 24 Nov 2023 14:20:22 -0000	[thread overview]
Message-ID: <170083562229.7.6753663629275309721@eaa400207d9c> (raw)

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

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202311-05
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                           https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: High
    Title: LinuxCIFS utils: Multiple Vulnerabilities
     Date: November 24, 2023
     Bugs: #842234
       ID: 202311-05

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

Synopsis
========

Multiple vulnerabilities have been discovered in LinuxCIFS utils, the
worst of which can lead to local root privilege escalation.

Background
==========

The LinuxCIFS utils are a collection of tools for managing Linux CIFS
Client Filesystems.

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

Package            Vulnerable    Unaffected
-----------------  ------------  ------------
net-fs/cifs-utils  < 6.15        >= 6.15

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

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

Impact
======

A stack-based buffer overflow when parsing the mount.cifs ip= command-
line argument could lead to local attackers gaining root privileges.

When verbose logging is enabled, invalid credentials file lines may be
dumped to stderr. This may lead to information disclosure in particular
conditions when the credentials file given is sensitive and contains '='
signs.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All LinuxCIFS utils users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=net-fs/cifs-utils-6.15"

References
==========

[ 1 ] CVE-2022-27239
      https://nvd.nist.gov/vuln/detail/CVE-2022-27239
[ 2 ] CVE-2022-29869
      https://nvd.nist.gov/vuln/detail/CVE-2022-29869

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

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

 https://security.gentoo.org/glsa/202311-05

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 2023 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:[~2023-11-24 14:21 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=170083562229.7.6753663629275309721@eaa400207d9c \
    --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