CVE Vulnerabilities

CVE-2020-25662

Improper Access Control

Published: Nov 05, 2020 | Modified: Nov 21, 2024
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
3.3 LOW
AV:A/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.3 MODERATE
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
NEGLIGIBLE
root.io logo minimus.io logo echo.ai logo

A Red Hat only CVE-2020-12352 regression issue was found in the way the Linux kernels Bluetooth stack implementation handled the initialization of stack memory when handling certain AMP packets. This flaw allows a remote attacker in an adjacent range to leak small portions of stack memory on the system by sending specially crafted AMP packets. The highest threat from this vulnerability is to data confidentiality.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
Enterprise_linuxRedhat8.3 (including)8.3 (including)
Red Hat Enterprise Linux 8RedHatkernel-rt-0:4.18.0-240.1.1.rt7.55.el8_3*
Red Hat Enterprise Linux 8RedHatkernel-0:4.18.0-240.1.1.el8_3*
LinuxUbuntutrusty*
Linux-awsUbuntutrusty*
Linux-azureUbuntutrusty*
Linux-hweUbuntubionic*
Linux-hweUbuntuesm-infra/bionic*
Linux-lts-xenialUbuntutrusty*
Linux-raspi2Ubuntuesm-infra/focal*
Linux-raspi2Ubuntufocal*

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