From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202402-15 ] e2fsprogs: Arbitrary Code Execution
Date: Sun, 18 Feb 2024 08:03:39 -0000 [thread overview]
Message-ID: <170824342005.8.8954539649512984269@987c7955d8b1> (raw)
[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202402-15
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: e2fsprogs: Arbitrary Code Execution
Date: February 18, 2024
Bugs: #838388
ID: 202402-15
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in e2fsprogs which can lead to
arbitrary code execution.
Background
==========
e2fsprogs is a set of utilities for maintaining the ext2, ext3 and ext4
file systems.
Affected packages
=================
Package Vulnerable Unaffected
---------------- ------------ ------------
sys-fs/e2fsprogs < 1.46.6 >= 1.46.6
Description
===========
Multiple vulnerabilities have been discovered in e2fsprogs. Please
review the CVE identifiers referenced below for details.
Impact
======
An out-of-bounds read/write vulnerability was found in e2fsprogs. This
issue leads to a segmentation fault and possibly arbitrary code
execution via a specially crafted filesystem.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All e2fsprogs users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-fs/e2fsprogs-1.46.6"
References
==========
[ 1 ] CVE-2022-1304
https://nvd.nist.gov/vuln/detail/CVE-2022-1304
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202402-15
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-02-18 8:04 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=170824342005.8.8954539649512984269@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