CVE Vulnerabilities

CVE-2020-0559

Incorrect Permission Assignment for Critical Resource

Published: Aug 13, 2020 | Modified: Apr 28, 2022
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.6 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Insecure inherited permissions in some Intel(R) PROSet/Wireless WiFi products on Windows* 7 and 8.1 before version 21.40.5.1 may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Ac_3165_firmware Intel * *
Ac_3168_firmware Intel * *
Ac_7265_firmware Intel * *
Ac_8260_firmware Intel * *
Ac_8265_firmware Intel * *
Ac_9260_firmware Intel * *
Ac_9461_firmware Intel * *
Ac_9462_firmware Intel * *
Ac_9560_firmware Intel * *
Ax200_firmware Intel * *
Ax201_firmware Intel * *

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References