CVE-2024-30369VulnerabilityPublished 6 Jun 2024Updated 2 Aug 2024

CVE-2024-30369: A10 Thunder ADC · Incorrect Permissions

Affects A10 Thunder ADCSource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
A10 Thunder ADC	Affected =6.0.2	Fixed in–

AI-suggested

To mitigate CVE-2024-30369, organizations should: 1) Immediately restrict local access to A10 Thunder ADC devices to trusted administrators only, minimizing the risk of low-privileged code execution. 2) Monitor and audit local user activities and file permission changes on the ADC systems to detect suspicious behavior. 3) Apply principle of least privilege rigorously, ensuring that users and processes have only the permissions necessary for their roles. 4) Engage with A10 Networks support to obtain any available patches or security advisories addressing this vulnerability and apply them promptly once released. 5) Implement network segmentation to isolate ADC devices from less trusted network zones, reducing the attack surface. 6) Use host-based intrusion detection systems (HIDS) on ADC appliances if supported, to alert on unauthorized privilege escalations or file permission modifications. 7) Regularly review and harden the configuration of the ADC devices, including installer and management components, to prevent exploitation of permission misconfigurations. 8) Prepare incident response plans specific to ADC compromise scenarios to enable rapid containment and recovery.

Description

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.

Impact

The impact of CVE-2024-30369 is substantial for organizations deploying A10 Thunder ADC appliances. Successful exploitation allows an attacker with limited local access to gain root privileges, effectively taking full control of the device. This can lead to unauthorized disclosure of sensitive data, manipulation or disruption of network traffic, and potential pivoting to other internal systems. Since ADCs are often positioned in critical network paths for load balancing and security functions, compromise can degrade service availability and integrity, impacting business continuity. The elevated privileges also enable attackers to install persistent backdoors or disrupt security controls, increasing the risk of prolonged undetected intrusions. Organizations relying on A10 Thunder ADC for application delivery, especially in sectors like finance, healthcare, telecommunications, and government, face heightened risk due to the critical nature of these systems.

Summary

CVE-2024-30369 is a vulnerability classified under CWE-732 (Incorrect Permission Assignment for Critical Resource) affecting A10 Thunder ADC version 6.0.2 build 68. The vulnerability stems from improper file permissions set on an installer component, which can be manipulated by a local attacker who already has limited code execution capabilities on the device. By exploiting this misconfiguration, the attacker can escalate privileges to root, thereby gaining full control over the affected system. This escalation enables execution of arbitrary code with the highest system privileges, compromising the device's confidentiality, integrity, and availability. The vulnerability does not require user interaction but does require local access and some level of prior code execution capability. The CVSS v3.0 score is 7.8, reflecting high severity due to the potential impact and relatively low complexity of exploitation. While no public patches or known exploits are currently available, the vulnerability was assigned by the Zero Day Initiative (ZDI) as ZDI-CAN-22754 and published in June 2024. Given the critical role of A10 Thunder ADC devices in application delivery and network traffic management, this vulnerability poses a significant risk if exploited.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
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.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 14:41 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats