CVE Vulnerabilities

CVE-2024-30369

Incorrect Permission Assignment for Critical Resource

Published: Jun 06, 2024 | Modified: Sep 24, 2024
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
RedHat/V2
RedHat/V3
Ubuntu

A10 Thunder ADC Incorrect Permission Assignment Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of A10 Thunder ADC. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

The specific flaw exists within the installer. The issue results from incorrect permissions on a file. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of root. Was ZDI-CAN-22754.

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
Advanced_core_operating_system A10networks 4.1.4 (including) 4.1.4 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1 (including) 4.1.4-gr1 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p1 (including) 4.1.4-gr1-p1 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p10 (including) 4.1.4-gr1-p10 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p11 (including) 4.1.4-gr1-p11 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p12 (including) 4.1.4-gr1-p12 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p13 (including) 4.1.4-gr1-p13 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p2 (including) 4.1.4-gr1-p2 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p3 (including) 4.1.4-gr1-p3 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p4 (including) 4.1.4-gr1-p4 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p5 (including) 4.1.4-gr1-p5 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p6 (including) 4.1.4-gr1-p6 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p7 (including) 4.1.4-gr1-p7 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p8 (including) 4.1.4-gr1-p8 (including)
Advanced_core_operating_system A10networks 4.1.4-gr1-p9 (including) 4.1.4-gr1-p9 (including)
Advanced_core_operating_system A10networks 4.1.4-p1 (including) 4.1.4-p1 (including)
Advanced_core_operating_system A10networks 4.1.4-p2 (including) 4.1.4-p2 (including)
Advanced_core_operating_system A10networks 4.1.4-p3 (including) 4.1.4-p3 (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