CVE-2024-30369 json
A10 Thunder ADC Incorrect Permission Assignment Local Privilege Escalation Vulnerability
published 2y ago modified 4mo ago also EUVD-2024-28290
- cvss
- 7.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- a10networks thunder_adc 4.1.4-gr1-p14, 5.2.1-p10, 6.0.3-p1
Is CVE-2024-30369 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- A10 Thunder ADC
- a10networks thunder_adc
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
support.a10networks.com
/support/security_advisory/cve-2024-30368-cve-2024-30369
vendor-advisory
-
zerodayinitiative.com
/advisories/ZDI-24-525/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2024-30369
- NVD CVE-2024-30369
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.