CVE Vulnerabilities

CVE-2024-26234

Improper Access Control

Published: Apr 09, 2024 | Modified: Jan 08, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Proxy Driver Spoofing Vulnerability

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Windows_10_1507 Microsoft * 10.0.10240.20596 (excluding)
Windows_10_1607 Microsoft * 10.0.14393.6897 (excluding)
Windows_10_1809 Microsoft * 10.0.17763.5696 (excluding)
Windows_10_21h2 Microsoft * 10.0.19044.4291 (excluding)
Windows_10_22h2 Microsoft * 10.0.19045.4291 (excluding)
Windows_11_21h2 Microsoft * 10.0.22000.2899 (excluding)
Windows_11_22h2 Microsoft * 10.0.22621.3447 (excluding)
Windows_11_23h2 Microsoft * 10.0.22631.3447 (excluding)
Windows_server_2008 Microsoft –sp2 (including) –sp2 (including)
Windows_server_2008 Microsoft r2-sp1 (including) r2-sp1 (including)
Windows_server_2012 Microsoft - (including) - (including)
Windows_server_2012 Microsoft r2 (including) r2 (including)
Windows_server_2016 Microsoft * 10.0.14393.6897 (excluding)
Windows_server_2019 Microsoft * 10.0.17763.5696 (excluding)
Windows_server_2022 Microsoft * 10.0.20348.2402 (excluding)
Windows_server_2022_23h2 Microsoft * 10.0.25398.830 (excluding)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References