CVE-2015-1388
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 · uneditedThe "RAP console" feature in ArubaOS 5.x through 6.2.x, 6.3.x before 6.3.1.15, and 6.4.x before 6.4.2.4 on Aruba access points in Remote Access Point (AP) mode allows remote attackers to execute arbitrary commands via unspecified vectors.
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 confidenceThe RAP (Remote Access Point) console feature in ArubaOS versions 5.x through 6.2.x, 6.3.x before 6.3.1.15, and 6.4.x before 6.4.2.4 contains a command injection vulnerability allowing remote attackers to execute arbitrary commands on affected Aruba access points in RAP mode via unspecified vectors.
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<= 6.2.3.9= 6.1.3.0= 6.1.3.1= 6.1.3.2= 6.1.3.3= 6.1.3.4= 6.1.3.5= 6.1.3.6= 6.1.3.7= 6.1.3.8= 6.1.3.9= 6.2.3.1CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify ArubaOS versionExecute 'show version' command on the Aruba device CLI or check the version displayed in the web management interface under Maintenance > Controller > Controller VersionAffected if The installed version falls within 5.x through 6.2.x, or is 6.3.x before 6.3.1.15, or is 6.4.x before 6.4.2.4, or matches one of the specific affected versions: 6.1.3.0 through 6.1.3.9, 6.2.3.1, or 6.2.3.9 and below
-
Confirm device is in RAP modeCheck the device configuration for Remote Access Point mode status via 'show rap license' command or by reviewing the AP deployment mode in the controller web interface under Configuration > AP > AP InstallationAffected if The device is operating as a Remote Access Point (RAP) rather than a campus AP or other AP mode
-
Verify RAP console feature is enabledCheck the RAP console configuration using 'show rap-console' command or verify in the web interface under Configuration > AP > RAP Console to see if the feature is turned onAffected if The RAP console feature is enabled on the device
The device is affected if it runs a vulnerable ArubaOS version within the affected ranges, is operating in RAP mode, and has the RAP console feature enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade ArubaOS to version 6.3.1.15, 6.4.2.4, or later. If immediate upgrading is not feasible, disable the RAP console feature and restrict management interface access to trusted IP addresses or networks.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1388 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1388 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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