# CVE-2016-8271: Information disclosure in eSpace IAD V300R002C01SPC100 and earlier versions

> An attacker can access a special URL to view and download fault information from Huawei eSpace IAD devices, leading to information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 2 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vc9c-8mfm-6gqp

## What is CVE-2016-8271?

CVE-2016-8271 is a medium-severity vulnerability in eSpace IAD V300R002C01SPC100 and earlier versions, published on 2 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei eSpace IAD V300R002C01SPC100 and earlier versions have an information leak vulnerability; an attacker can check and download the fault information by accessing a special URL.

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

## Which versions are affected by CVE-2016-8271?

It affects 1 product.


Products: Huawei Espace Iad Firmware.

## How do I fix CVE-2016-8271?

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

## Is CVE-2016-8271 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8271 and fix it if it is affected.

What it is: CVE-2016-8271 is a medium-severity vulnerability in eSpace IAD V300R002C01SPC100 and earlier versions, published on 2 Apr 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-2016-8271 in the wild and no public exploit code.

Affected product: eSpace IAD V300R002C01SPC100 and earlier versions. 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-2016-8271/ (Markdown: https://insights.sbomify.com/CVE-2016-8271/index.md)
```

## Sources

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

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