Explore top 10 tips to secure your open-source projects now. Read More

×
Alerts This Week
Warning Icon 1 602
Alerts This Week
Warning Icon 1 602

Gentoo: GLSA-202107-31 High: Polkit Local Root Escalation Risk

gentoo
Calendar Grey July 12, 2021
Dist Gentoo Esm H88
An urgent security flaw in polkit could enable local users to gain root privileges on Gentoo platforms, necessitating prompt intervention through patching.
A vulnerability in polkit could lead to local root privilege escalation.

Summary

The function polkit_system_bus_name_get_creds_sync() was called without checking for error, and as such temporarily treats the authentication request as coming from root.

Resolution

All polkit users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-auth/polkit-0.119"

References

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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202107-31
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: High
Title: polkit: Privilege escalation
Date: July 13, 2021
Bugs: #794052
ID: 202107-31

Synopsis

A vulnerability in polkit could lead to local root privilege escalation.

Background

polkit is a toolkit for managing policies related to unprivileged processes communicating with privileged process.

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-auth/polkit < 0.119 >= 0.119

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.