selinux-policy up to 3.14 Configuration File .config/Yubico 2FA improper authentication

Summaryinfo

A vulnerability marked as critical has been reported in selinux-policy up to 3.14. This impacts an unknown function of the file .config/Yubico of the component Configuration File Handler. This manipulation causes improper authentication (2FA). This vulnerability appears as CVE-2020-24612. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability has been found in selinux-policy up to 3.14 and classified as critical. Affected by this vulnerability is an unknown code of the file .config/Yubico of the component Configuration File Handler. The manipulation with an unknown input leads to a improper authentication vulnerability (2FA). The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in the selinux-policy (aka Reference Policy) package 3.14 through 2020-08-24 because the .config/Yubico directory is mishandled. Consequently, when SELinux is in enforced mode, pam-u2f is not allowed to read the user's U2F configuration file. If configured with the nouserok option (the default when configured by the authselect tool), and that file cannot be read, the second factor is disabled. An attacker with only the knowledge of the password can then log in, bypassing 2FA.

The weakness was presented 08/24/2020. This vulnerability is known as CVE-2020-24612 since 08/24/2020. The exploitation appears to be difficult. An attack has to be approached locally. A single authentication is needed for exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 249836 (Linux Distros Unpatched Vulnerability : CVE-2020-24612), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (249836). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• selinux-policy

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 3.10
• 3.11
• 3.12
• 3.13
• 3.14

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion