# CVE-2015-6586: Information disclosure in n/a

> Remote attackers can obtain sensitive information from Huawei WLAN AC devices due to improper restriction of mDNS unicast queries.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7qqr-cp29-8p5x

## What is CVE-2015-6586?

CVE-2015-6586 is a high-severity vulnerability in n/a, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-6586?

It affects 3 products.


Products: Huawei Wlan Ac6005 Firmware, Huawei Wlan Ac6605 Firmware, Huawei Wlan Acu2 Firmware.

## How do I fix CVE-2015-6586?

No fix has been published for CVE-2015-6586 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-6586 being exploited?

There is no known exploitation of CVE-2015-6586 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6586 and fix it if it is affected.

What it is: CVE-2015-6586 is a high-severity vulnerability in n/a, published on 23 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6586 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-6586/ (Markdown: https://insights.sbomify.com/CVE-2015-6586/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-6586
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-6586
- OSV: https://osv.dev/vulnerability/CVE-2015-6586

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-6586/
Summaries are generated and may contain mistakes; the official description above is the record.