dbcve.org
Advanced Core Operating SystemOperating system · A10networks

CVE-2024-30368

HIGH · 8.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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 CsrRequestView Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of A10 Thunder ADC. Authentication is required to exploit this vulnerability. The specific flaw exists within the CsrRequestView class. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of a10user. Was ZDI-CAN-22517.

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 · high confidence

Command injection vulnerability in A10 Thunder ADC's CsrRequestView class allows authenticated remote attackers to execute arbitrary code by injecting unsanitized user input into a system call. The lack of proper input validation on user-supplied strings enables attackers to break out of intended command boundaries and execute commands as the a10user.

MitigationApply vendor-supplied patches for CVE-2024-30368 when available. Until then, restrict administrative access to trusted personnel only and monitor for suspicious command activity.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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
    Access the device CLI and run the command to display the system version (for example, 'show version' or 'display version'). Note the exact version number reported.
    Affected if The displayed version matches one of the affected versions: 4.1.4, 5.1.0, 5.2.0, 5.2.1, 6.0.0, 6.0.1, 6.0.2, or 6.0.3.
  2. Confirm web management interface is accessible
    Verify that the device's web-based management interface or API endpoint is reachable from the network. This may involve attempting to access the login page or checking if HTTP/HTTPS ports are listening.
    Affected if The web management interface is exposed and accessible to the network where untrusted users could potentially authenticate.
  3. Verify user authentication is enabled
    Check if local or remote user authentication (such as RADIUS, TACACS+, or local database) is configured and active for administrative access to the device.
    Affected if User authentication is configured and allows login by accounts that are not explicitly trusted or are unknown.
  4. Review for suspicious command execution logs
    Examine system logs, audit logs, or command history for unexpected or unauthorized commands, especially those involving shell execution, script invocations, or unusual system calls originating from the CsrRequestView functionality.
    Affected if Logs show commands or system calls that were not initiated by trusted administrators, or contain evidence of command injection attempts (such as unusual characters or unexpected command chaining).

If the device runs an affected ACOS version (4.1.4, 5.1.0, 5.2.0, 5.2.1, 6.0.0, 6.0.1, 6.0.2, or 6.0.3) AND has an accessible web management interface where untrusted users can authenticate, the environment is potentially affected by this vulnerability.

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-supplied patches for CVE-2024-30368 when available. Until then, restrict administrative access to trusted personnel only and monitor for suspicious command activity.

Fix this in Advanced Core Operating System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30368 — 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-30368 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