CVE Vulnerabilities

CVE-2023-28960

Incorrect Permission Assignment for Critical Resource

Published: Apr 17, 2023 | Modified: Apr 28, 2023
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

An Incorrect Permission Assignment for Critical Resource vulnerability in Juniper Networks Junos OS Evolved allows a local, authenticated low-privileged attacker to copy potentially malicious files into an existing Docker container on the local system. A follow-on administrator could then inadvertently start the Docker container leading to the malicious files being executed as root. This issue only affects systems with Docker configured and enabled, which is not enabled by default. Systems without Docker started are not vulnerable to this issue. This issue affects Juniper Networks Junos OS Evolved: 20.4 versions prior to 20.4R3-S5-EVO; 21.2 versions prior to 21.2R3-EVO; 21.3 versions prior to 21.3R3-EVO; 21.4 versions prior to 21.4R2-EVO. This issue does not affect Juniper Networks Junos OS Evolved versions prior to 19.2R1-EVO.

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
Junos_os_evolved Juniper 20.4 (including) 20.4 (including)
Junos_os_evolved Juniper 20.4-r1 (including) 20.4-r1 (including)
Junos_os_evolved Juniper 20.4-r1-s1 (including) 20.4-r1-s1 (including)
Junos_os_evolved Juniper 20.4-r1-s2 (including) 20.4-r1-s2 (including)
Junos_os_evolved Juniper 20.4-r2 (including) 20.4-r2 (including)
Junos_os_evolved Juniper 20.4-r2-s1 (including) 20.4-r2-s1 (including)
Junos_os_evolved Juniper 20.4-r2-s2 (including) 20.4-r2-s2 (including)
Junos_os_evolved Juniper 20.4-r2-s3 (including) 20.4-r2-s3 (including)
Junos_os_evolved Juniper 20.4-r3 (including) 20.4-r3 (including)
Junos_os_evolved Juniper 20.4-r3-s1 (including) 20.4-r3-s1 (including)
Junos_os_evolved Juniper 20.4-r3-s2 (including) 20.4-r3-s2 (including)
Junos_os_evolved Juniper 20.4-r3-s3 (including) 20.4-r3-s3 (including)
Junos_os_evolved Juniper 20.4-r3-s4 (including) 20.4-r3-s4 (including)
Junos_os_evolved Juniper 21.2 (including) 21.2 (including)
Junos_os_evolved Juniper 21.2-r1 (including) 21.2-r1 (including)
Junos_os_evolved Juniper 21.2-r1-s1 (including) 21.2-r1-s1 (including)
Junos_os_evolved Juniper 21.2-r1-s2 (including) 21.2-r1-s2 (including)
Junos_os_evolved Juniper 21.2-r2 (including) 21.2-r2 (including)
Junos_os_evolved Juniper 21.2-r2-s1 (including) 21.2-r2-s1 (including)
Junos_os_evolved Juniper 21.2-r2-s2 (including) 21.2-r2-s2 (including)
Junos_os_evolved Juniper 21.3 (including) 21.3 (including)
Junos_os_evolved Juniper 21.3-r1 (including) 21.3-r1 (including)
Junos_os_evolved Juniper 21.3-r1-s1 (including) 21.3-r1-s1 (including)
Junos_os_evolved Juniper 21.3-r2 (including) 21.3-r2 (including)
Junos_os_evolved Juniper 21.3-r2-s1 (including) 21.3-r2-s1 (including)
Junos_os_evolved Juniper 21.3-r2-s2 (including) 21.3-r2-s2 (including)
Junos_os_evolved Juniper 21.4 (including) 21.4 (including)
Junos_os_evolved Juniper 21.4-r1 (including) 21.4-r1 (including)
Junos_os_evolved Juniper 21.4-r1-s1 (including) 21.4-r1-s1 (including)
Junos_os_evolved Juniper 21.4-r1-s2 (including) 21.4-r1-s2 (including)

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