Command InjectionWeakness · CWE-77

CVE-2024-47461

HIGH · 7.2 CVSS v3.1 Published 2024-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
An authenticated command injection vulnerability exists in the Instant AOS-8 and AOS-10 command line interface. A successful exploitation of this vulnerability results in the ability to execute arbitrary commands as a privileged user on the underlying operating system. This allows an attacker to fully compromise the underlying host operating system.

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

An authenticated command injection vulnerability exists in the CLI of Aruba Instant AOS-8 and AOS-10. Successful exploitation allows an authenticated attacker to inject and execute arbitrary operating system commands with privileged (root) user permissions, resulting in full compromise of the underlying host.

MitigationApply available vendor patches for AOS-8 and AOS-10. Until patches are applied, limit CLI access to only trusted, authorized administrators 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.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Aruba Instant AOS deployment
    Confirm the device runs Aruba Instant AOS-8 or AOS-10 by checking the system firmware or controller interface for the product name and version string
    Affected if Device is not running Aruba Instant AOS-8 or AOS-10 (not affected)
  2. Determine installed AOS version
    Run 'show version' or access the controller GUI dashboard to retrieve the exact AOS version number
    Affected if Version cannot be determined or is not within AOS-8 or AOS-10 release trains
  3. Verify CLI access is enabled
    Check the Instant AP or controller configuration for CLI (SSH or console) access settings; confirm user accounts with CLI privileges exist
    Affected if CLI access is disabled and no CLI users are configured (low likelihood of exploitation)
  4. Review CLI command logs
    Examine CLI audit logs, system logs, or command history for unexpected or suspicious commands that may indicate exploitation attempts
    Affected if Unauthorized or unexpected commands appear in CLI logs

The environment is likely affected if it runs Aruba Instant AOS-8 or AOS-10 with CLI access enabled, since exploitation requires authenticated CLI access to inject arbitrary commands.

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 available vendor patches for AOS-8 and AOS-10. Until patches are applied, limit CLI access to only trusted, authorized administrators and monitor for suspicious command activity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-47461 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