dbcve.org
Edgeconnect EnterpriseWeb browser · Arubanetworks

CVE-2023-30506

HIGH · 8.8 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to after 9.2.3.0 or later.
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
Vulnerabilities exist in the Aruba EdgeConnect Enterprise command line interface that allow remote authenticated users to run arbitrary commands on the underlying host. Successful exploitation of these vulnerabilities result in the ability to execute arbitrary commands as root on the underlying operating system leading to complete system compromise.

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 the Aruba EdgeConnect Enterprise CLI allows remote authenticated users to execute arbitrary commands as root on the underlying operating system, resulting in complete system compromise.

MitigationApply vendor-provided patches for Aruba EdgeConnect Enterprise; restrict CLI access to trusted users only and implement network segmentation to limit exposure.

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
Edgeconnect EnterpriseWeb browser
Affected:<= 9.0.8.0>= 9.1.0.0, <= 9.1.5.0>= 9.2.0.0, <= 9.2.3.0

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. Determine EdgeConnect Enterprise version
    Log into the EdgeConnect CLI or web UI and locate the software version displayed in the system information or about section. Alternatively, check the output of 'show version' command via CLI.
    Affected if The installed version falls within <= 9.0.8.0, >= 9.1.0.0 through <= 9.1.5.0, or >= 9.2.0.0 through <= 9.2.3.0.
  2. Verify CLI access is enabled
    Check the EdgeConnect configuration for the enablement status of the CLI service. In the web UI, navigate to System > Administration > CLI Access or similar. From CLI, use 'show cli status' or 'show management' commands if available.
    Affected if The CLI service is enabled and accessible.
  3. Confirm network exposure of CLI service
    Review firewall rules, access profiles, or management interface bindings to determine if the CLI is reachable from network segments outside the trusted administration zone. Check for any 'permit' rules allowing external IP ranges to port 22 (SSH) or the CLI management port.
    Affected if The CLI is exposed to untrusted network segments or the internet.
  4. Identify authentication methods for CLI
    Inspect the CLI authentication configuration to see which user accounts have CLI access privileges. Look for local users, RADIUS, or TACACS+ integrations that grant CLI access.
    Affected if Remote authenticated users are permitted to access the CLI.

A user is affected if their EdgeConnect Enterprise version is within the affected ranges AND the CLI is accessible to remote authenticated users on an exposed network interface.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 9.2.3.0
Interim mitigation

Apply vendor-provided patches for Aruba EdgeConnect Enterprise; restrict CLI access to trusted users only and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

9.2.4.0 or later (or latest 9.x release)

  1. 1. Identify the current EdgeConnect Enterprise version installed using 'show version' or similar CLI command
  2. 2. Based on the current version line, plan upgrade path: if on 9.0.x, upgrade to 9.0.9.0 or later; if on 9.1.x, upgrade to 9.1.6.0 or later; if on 9.2.x, upgrade to 9.2.4.0 or later
  3. 3. Download the appropriate updated EdgeConnect Enterprise image from the Aruba Networks support portal (https://asp.arubanetworks.com)
  4. 4. Review upgrade prerequisites in Aruba documentation, including backup requirements
  5. 5. Upload the new software image to the EdgeConnect device
  6. 6. Schedule maintenance window as upgrade may cause service interruption
  7. 7. Execute upgrade command (e.g., 'upgrade software' or equivalent)
  8. 8. Verify successful upgrade by confirming new version post-reboot
Caveat Review Aruba upgrade documentation for any migration steps between major versions; ensure compatibility with integration components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Edgeconnect Enterprise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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