dbcve.org
Aruba InstantApplication · Arubanetworks

CVE-2018-7082

HIGH · 7.2 CVSS v3.1 Published 2019-05-10
Fix available
A fix is available. Upgrade to 4.2.4.12 / 6.5.4.11 or later.
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
A command injection vulnerability is present in Aruba Instant that permits an authenticated administrative user to execute arbitrary commands on the underlying operating system. A malicious administrator could use this ability to install backdoors or change system configuration in a way that would not be logged. Workaround: None. Resolution: Fixed in Aruba Instant 4.2.4.12, 6.5.4.11, 8.3.0.6, and 8.4.0.0

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 Aruba Instant allowing an authenticated administrative user to execute arbitrary commands on the underlying operating system, enabling installation of backdoors or unlogged configuration changes.

MitigationUpgrade Aruba Instant to one of the fixed versions (4.2.4.12, 6.5.4.11, 8.3.0.6, or 8.4.0.0). Since no workaround exists and exploitation by a malicious administrator leaves no logs, a compromise assessment should be performed before patching.

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
Aruba InstantApplication
Affected:>= 4.0, < 4.2.4.12>= 6.5.0, < 6.5.4.11>= 8.3.0.0, < 8.3.0.6>= 8.4.0, < 8.4.0.1
Scalance W1750d FirmwareOperating system
Affected:< 8.4.0.1

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 version
    Log into the Aruba Instant CLI and run 'show version' or access the WebUI and check the Dashboard or About page for the firmware version
    Affected if The displayed version falls within any of these ranges: >= 4.0 and < 4.2.4.12, >= 6.5.0 and < 6.5.4.11, >= 8.3.0.0 and < 8.3.0.6, or >= 8.4.0 and < 8.4.0.1
  2. Identify Siemens Scalance W1750d version
    Access the device web interface or CLI and retrieve the firmware version from the system information or status page
    Affected if The firmware version is earlier than 8.4.0.1
  3. Check for enabled management interfaces
    Run 'show running-config' in Aruba Instant CLI or review the WebUI under Configuration > Network > Interfaces to see which management interfaces (HTTP/HTTPS/SSH) are enabled and accessible
    Affected if Any management interface (especially HTTP or HTTPS) is exposed to untrusted networks and the version is vulnerable
  4. Verify administrative account integrity
    Review the list of local administrative users via 'show users' in CLI or Configuration > Security > Management User in the WebUI, and check for any unexpected accounts or configuration changes
    Affected if Unexpected admin accounts exist or configuration changes are found that were not made by authorized personnel
  5. Assess exposure of management interface
    Review firewall policies, ACLs, or network segmentation to determine if the Aruba Instant or Scalance management interface is reachable from outside the trusted network
    Affected if The management interface (ports 80, 443, or 22) is accessible from untrusted networks or the internet

The environment is affected if Aruba Instant or Siemens Scalance W1750d is running any version below the fixed releases (4.2.4.12, 6.5.4.11, 8.3.0.6, or 8.4.0.1) and the management interface is accessible to the attacker.

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
Upgrade available Upgrade to 4.2.4.12 / 6.5.4.11 / 8.3.0.6 or later
Fixed in 4.2.4.126.5.4.118.3.0.6
Interim mitigation

Upgrade Aruba Instant to one of the fixed versions (4.2.4.12, 6.5.4.11, 8.3.0.6, or 8.4.0.0). Since no workaround exists and exploitation by a malicious administrator leaves no logs, a compromise assessment should be performed before patching.

Fix this in Aruba Instant Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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