dbcve.org
Advanced Core Operating SystemOperating system · A10networks

CVE-2024-30369

HIGH · 7.8 CVSS v3.1 Published 2024-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A10 Thunder ADC contains a local privilege escalation vulnerability in its installer where incorrect file permissions allow a low-privileged attacker to modify or replace a file and execute it with root privileges. The attacker first needs low-privileged code execution capability on the target system.

MitigationApply vendor patch when available. As a temporary mitigation, identify the file with incorrect permissions post-installation and restrict write access to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advanced Core Operating SystemOperating system
Affected:= 4.1.4= 5.1.0= 5.2.0= 5.2.1= 6.0.0= 6.0.1= 6.0.2= 6.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed A10 ACOS version
    Run command to display the installed version of A10 Advanced Core Operating System (e.g., 'show version' or 'acos-cli --version' depending on access method). Compare the output against the affected versions: 4.1.4, 5.1.0, 5.2.0, 5.2.1, 6.0.0, 6.0.1, 6.0.2, 6.0.3.
    Affected if The installed version matches one of the listed affected versions.
  2. Locate installer files and directories
    Search for installer-related files and directories on the system. Common locations may include /opt, /usr/local, /tmp, or installation staging directories. Use 'find' commands to locate files with 'install' or 'setup' in their names.
    Affected if Installer files exist on the system and are accessible after initial installation.
  3. Inspect file permissions on installer binaries or scripts
    List file permissions using 'ls -la' on identified installer files. Look for files that are owned by root but have world-writable or group-writable permissions (e.g., -rwxrwxrwx, -rwxrwxrwx).
    Affected if Any installer file executable by root is writable by a low-privileged user (permissions show w for others or group).
  4. Verify ownership of installer executables
    Check the owner of installer files using 'ls -ln'. Identify files owned by root but with permissions allowing modification by non-root users.
    Affected if Files are owned by root but allow write access from the low-privileged user context.
  5. Check for script or binary substitution capability
    Examine if a low-privileged user can create or overwrite files in directories containing installer scripts or binaries. Attempt to verify if the low-privileged user has write access to directories holding executable installer components.
    Affected if A low-privileged user can write to directories containing root-owned executable files used during installation or post-installation processes.

A system is affected if it runs an affected ACOS version (4.1.4, 5.1.0, 5.2.0, 5.2.1, 6.0.0-6.0.3) AND contains installer files with overly permissive write access that a low-privileged user can exploit to escalate privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available. As a temporary mitigation, identify the file with incorrect permissions post-installation and restrict write access to prevent exploitation.

Fix this in Advanced Core Operating System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30369 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data