Alerts This Week
Warning Icon 1 692
Alerts This Week
Warning Icon 1 692

Gentoo: GLSA-202012-17 Low Severity: D-Bus Denial Of Service Threat

gentoo
Calendar Grey December 23, 2020
Dist Gentoo Esm H88
The Gentoo Linux team issued an advisory on a minor D-Bus denial of service vulnerability. Users should adhere to the suggested update procedures to reduce risks
A local Denial of Service vulnerability was discovered in D-Bus.

Summary

It was discovered that D-Bus did not properly handle the situation when two usernames have the same numeric UID.

Resolution

All D-Bus users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-apps/dbus-1.12.20"

References

[ 1 ] dbus 1.12.20 security update announcement https://lists.freedesktop.org/archives/ftp-release/2020-July/000758.html

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202012-17
style>.gentoo_availability{display:block;}

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.

Severity
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: D-Bus: Denial of service
Date: December 23, 2020
Bugs: #755392
ID: 202012-17

Synopsis

A local Denial of Service vulnerability was discovered in D-Bus.

Background

D-Bus is a message bus system which processes can use to talk to each other.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 sys-apps/dbus < 1.12.20 >= 1.12.20

Impact

===== An attacker could possibly cause a Denial of Service condition or trigger other undefined behavior, possibly including incorrect authorization decisions.

Workaround

There is no known workaround at this time.

Related News

Your message here