VYPR
Unrated severityNVD Advisory· Published Mar 8, 2022· Updated Feb 13, 2025

CVE-2021-3981

CVE-2021-3981

Description

A flaw in grub2 configuration file permissions allows unprivileged users to read grub.cfg, potentially exposing encrypted passwords.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A flaw in grub2 configuration file permissions allows unprivileged users to read grub.cfg, potentially exposing encrypted passwords.

Vulnerability

The GRUB2 configuration file grub.cfg is created with incorrect permissions (0644) instead of restricted permissions, allowing any local unprivileged user to read its contents. This affects GRUB2 versions 2.06 and earlier [4]. The file may contain encrypted passwords used for boot menu protection.

Exploitation

An unprivileged user with local access to the system can simply read the file, typically located at /boot/grub2/grub.cfg or similar, due to the world-readable permission [4]. No authentication beyond a standard user account is required, and no special privileges or user interaction are needed.

Impact

A local attacker can read encrypted passwords stored in grub.cfg. While the passwords are hashed, they may be susceptible to offline brute-force attacks, potentially allowing the attacker to bypass boot-level authentication and gain unauthorized access to the system.

Mitigation

The issue has been fixed upstream, but no official release with the fix is currently available [4]. As a workaround, administrators can manually set restrictive permissions on grub.cfg (e.g., chmod 600). Gentoo GLSA 202209-12 recommends upgrading to sys-boot/grub-2.06-r3 [3]. There is no KEV listing.

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

21

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

4

News mentions

0

No linked articles in our index yet.