CVE-2015-6592
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 · uneditedHuawei UAP2105 before V300R012C00SPC160(BootRom) does not require authentication to the serial port or the VxWorks shell.
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 Huawei UAP2105 devices running BootRom versions before V300R012C00SPC160 contain an authentication bypass vulnerability. The serial port and VxWorks shell can be accessed without any authentication credentials, allowing unauthenticated attackers to potentially gain full control of the device.
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= v300r011c0spc100= v300r011c01b028= v300r011c01b030= v300r011c01spc110CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label or access the device management interface to confirm the model is Huawei UAP2105Affected if The device is not a Huawei UAP2105 model - this CVE does not apply
-
Check the BootRom versionAccess the device console via serial port or login to the device management system and look for the BootRom version information, typically displayed during device startup or in system information pagesAffected if BootRom version is before V300R012C00SPC160, or matches one of these affected versions: v300r011c0spc100, v300r011c01b028, v300r011c01b030, v300r011c01spc110
-
Test serial port access without credentialsConnect to the device serial port (usually RJ45 or DB9 connector) and attempt to access the console without providing any username or password when promptedAffected if Serial port grants access to the device shell or boot menu without requiring any authentication credentials
-
Test VxWorks shell accessibilityAfter connecting via serial port or network, attempt to access the VxWorks shell prompt (often indicated by a 'VxWorks>' or similar prompt) without providing login credentialsAffected if The VxWorks shell is accessible and accepts commands without authentication
The device is affected if it is a Huawei UAP2105 with BootRom version earlier than V300R012C00SPC160, and either the serial port or VxWorks shell can be accessed without providing authentication credentials.
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 the device BootRom firmware to version V300R012C00SPC160 or later. If immediate patching is not feasible, physically secure the serial port and disable the VxWorks shell if not required for legitimate administration.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6592 — 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-6592 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