Alerts This Week
Warning Icon 1 764
Alerts This Week
Warning Icon 1 764

Gentoo: High Risk of Systemd Heap Exploit as of 202003-20 Update

gentoo
Calendar Grey March 15, 2020
Dist Gentoo Esm H88
A memory corruption flaw in systemd leads to a use-after-free vulnerability, enabling remote attackers to run arbitrary commands, posing risks for Gentoo users. Immediate updates are advised
A heap use-after-free flaw in systemd at worst might allow an attacker to execute arbitrary code.

Summary

It was found that systemd incorrectly handled certain Polkit queries.

Resolution

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

References

[ 1 ] CVE-2020-1712 https://nvd.nist.gov/vuln/detail/CVE-2020-1712

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202003-20
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: systemd: Heap use-after-free
Date: March 15, 2020
Bugs: #708806
ID: 202003-20

Synopsis

A heap use-after-free flaw in systemd at worst might allow an attacker to execute arbitrary code.

Background

A system and service manager.

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/systemd < 244.3 >= 244.3

Impact

===== A local unprivileged user, by sending a specially crafted Polkit query, could possibly execute arbitrary code with the privileges of the process, escalate privileges or cause a Denial of Service condition.

Workaround

There is no known workaround at this time.

Your message here