Gentoo: GLSA-202105-09: BusyBox: Denial of service

Advisories

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 202105-09
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Low
     Title: BusyBox: Denial of service
      Date: May 26, 2021
      Bugs: #777255
        ID: 202105-09

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

Synopsis
========

A vulnerability in BusyBox might allow remote attackers to cause a
Denial of Service condition.

Background
==========

BusyBox is a set of tools for embedded systems and is a replacement for
GNU Coreutils.

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

     -------------------------------------------------------------------
      Package              /     Vulnerable     /            Unaffected
     -------------------------------------------------------------------
   1  sys-apps/busybox             < 1.32.1                  >= 1.32.1

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

It was discovered that BusyBox mishandled the error bit on the
huft_build result pointer when decompressing GZIP compressed data.

Impact
======

A remote attacker could entice a user to open a specially crafted GZIP
file using BusyBox, possibly resulting in a Denial of Service
condition.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All BusyBox users should upgrade to the latest version:

   # emerge --sync
   # emerge --ask --oneshot --verbose ">=sys-apps/busybox-1.32.1"

References
==========

[ 1 ] CVE-2021-28831
       https://nvd.nist.gov/vuln/detail/CVE-2021-28831

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

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

  https://security.gentoo.org/glsa/202105-09

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
[email protected] or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2021 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

Gentoo: GLSA-202105-09: BusyBox: Denial of service

Summary

It was discovered that BusyBox mishandled the error bit on the huft_build result pointer when decompressing GZIP compressed data.

Resolution

All BusyBox users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=sys-apps/busybox-1.32.1"

References

[ 1 ] CVE-2021-28831 https://nvd.nist.gov/vuln/detail/CVE-2021-28831

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202105-09

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 [email protected] or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Low
Title: BusyBox: Denial of service
Issued Date: May 26, 2021
Bugs: #777255
ID: 202105-09

Synopsis

A vulnerability in BusyBox might allow remote attackers to cause a Denial of Service condition.

Background

BusyBox is a set of tools for embedded systems and is a replacement for GNU Coreutils.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-apps/busybox < 1.32.1 >= 1.32.1

Impact

A remote attacker could entice a user to open a specially crafted GZIP file using BusyBox, possibly resulting in a Denial of Service condition.

Workaround

There is no known workaround at this time.

We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.