CVE-2015-6586
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 mDNS module in Huawei WLAN AC6005, AC6605, and ACU2 devices with software before V200R006C00SPC100 allows remote attackers to obtain sensitive information by leveraging failure to restrict processing of mDNS unicast queries to the link local network.
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 mDNS module in Huawei WLAN AC6005, AC6605, and ACU2 devices fails to restrict processing of mDNS unicast queries to the link-local network, allowing remote attackers to query sensitive network service information from outside the local network segment.
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<= v200r005c00<= v200r005c10<= v200r006c00<= v200r005c00<= v200r005c10<= v200r006c00<= v200r005c00<= v200r005c10<= v200r006c00CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the device and run 'display device' or 'display version' to confirm the model is ACU2, AC6005, or AC6605Affected if Device model is ACU2, AC6005, or AC6605
-
Check the firmware versionRun 'display version' or 'display firmware version' to obtain the current firmware versionAffected if Firmware version is v200r005c00, v200r005c10, or v200r006c00 or lower
-
Confirm mDNS feature is enabledRun 'display current-configuration | include mdns' or check the mDNS service status to see if mDNS processing is active on the deviceAffected if mDNS module is enabled and processing queries
-
Check mDNS unicast query configurationRun 'display mdns configuration' or examine mDNS settings to determine if unicast queries from non-link-local sources are being processedAffected if mDNS is configured to accept unicast queries from outside the link-local network (no ACL or filter restricts mDNS to local subnet)
-
Verify network filtering on mDNS trafficCheck for any ACL rules or packet filtering applied to mDNS traffic (port 5353) that would restrict it to link-local networks onlyAffected if No ACL or filter is configured to restrict mDNS to link-local scope
You are affected if you have an ACU2, AC6005, or AC6605 device running firmware v200r005c00, v200r005c10, or v200r006c00 with mDNS enabled and no link-local restriction configured on mDNS unicast query processing.
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 dataUpdate affected devices to firmware version V200R006C00SPC100 or later to enforce link-local restriction on mDNS unicast query processing.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6586 — 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-6586 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