dbcve.org
ArubaosOperating system · Arubanetworks

CVE-2024-31483

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 8.6.0.24 / 8.10.0.11 or later.
See remediation →
71/100
Remediation priority · Elevated
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 sensitive information disclosure vulnerability exists in the CLI service accessed via the PAPI protocol. Successful exploitation of this vulnerability results in the ability to read arbitrary files in the underlying 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

This is an authenticated arbitrary file read vulnerability in the CLI service accessible through the PAPI protocol. An attacker with valid credentials can exploit this vulnerability to read any file on the underlying operating system, potentially exposing sensitive data such as configuration files, credentials, or other system files.

MitigationApply vendor-provided patches for this vulnerability. If a patch is unavailable, implement strict access controls and input validation on the PAPI protocol endpoints, and consider network segmentation to limit exposure of the CLI service.

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
ArubaosOperating system
Affected:>= 10.3.0.0, < 10.4.1.1>= 10.5.0.0, < 10.5.1.1
InstantosOperating system
Affected:>= 6.4.0.0, < 8.6.0.24>= 8.7.0.0, < 8.10.0.11

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
None
Availability
None

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

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 the installed ArubaOS or InstantOS version
    Run 'show version' or 'get version' command on the device CLI, or check via the WebUI dashboard
    Affected if The version falls within >= 10.3.0.0 and < 10.4.1.1, or >= 10.5.0.0 and < 10.5.1.1 for ArubaOS; or >= 6.4.0.0 and < 8.6.0.24, or >= 8.7.0.0 and < 8.10.0.11 for InstantOS
  2. Verify the PAPI protocol service is enabled
    Check device configuration for 'papi' or 'CLI service' settings. Run 'show papi status' or 'show web-server | include papi' if available
    Affected if The PAPI service is enabled and listening on the device
  3. Determine if PAPI is accessible from untrusted networks
    Review ACLs, firewall rules, and management interface access lists. Check if port 8211 (typical PAPI port) or the configured PAPI port is exposed to non-management networks
    Affected if The PAPI service is reachable from network segments that are not strictly trusted or management networks
  4. Confirm valid operator accounts exist
    List local operator accounts via 'show user' or 'show aaa local-user' commands. Review authentication server configurations for external auth sources
    Affected if There are valid local or remote user accounts that could be used to authenticate to the CLI/PAPI service
  5. Check for evidence of unauthorized file access
    Review system logs and audit logs for unusual file read operations, especially targeting /etc/shadow, configuration files, or system directories
    Affected if Logs show file read operations from CLI users that were not initiated by legitimate administrators

You are affected if your device runs a vulnerable ArubaOS or InstantOS version AND the PAPI/CLI service is accessible with valid credentials from your network

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 8.6.0.24 / 8.10.0.11 / 10.4.1.1 or later
Fixed in 8.6.0.248.10.0.1110.4.1.1
Interim mitigation

Apply vendor-provided patches for this vulnerability. If a patch is unavailable, implement strict access controls and input validation on the PAPI protocol endpoints, and consider network segmentation to limit exposure of the CLI service.

Recommended fix High confidence

ArubaOS 10.4.1.1 or 10.5.1.1; InstantOS 8.6.0.24 or 8.10.0.11

  1. 1. Identify the current ArubaOS or InstantOS version running on the affected device using 'show version' in the CLI
  2. 2. Obtain the fixed firmware from HPE Aruba support portal (support.hpe.com or www.arubanetworks.com)
  3. 3. For ArubaOS: upgrade to version 10.4.1.1 (if currently on 10.3.x) or 10.5.1.1 (if currently on 10.5.x)
  4. 4. For InstantOS: upgrade to version 8.6.0.24 (if currently on 6.4.x-8.5.x) or 8.10.0.11 (if currently on 8.7.x-8.9.x)
  5. 5. Upload the firmware file via the device WebUI or CLI using 'upgrade-software' command
  6. 6. Reboot the device to apply the new firmware
  7. 7. Verify the new version is installed using 'show version'
  8. 8. Confirm the vulnerability is remediated by verifying the PAPI protocol CLI no longer allows arbitrary file reads

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

Fix this in Arubaos Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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