# CVE-2017-15327: Missing authorization in S12700, S7700, S9700

> A missing authorization check in Huawei switches allows normal users to access restricted information, leading to information disclosure.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-943p-33cc-x6w3

## What is CVE-2017-15327?

CVE-2017-15327 is a medium-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. S12700, S7700, S9700, published on 11 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

S12700 V200R005C00, V200R006C00, V200R006C01, V200R007C00, V200R007C01, V200R007C20, V200R008C00, V200R008C06, V200R009C00, V200R010C00, S7700 V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R006C01, V200R007C00, V200R007C01, V200R008C00, V200R008C06, V200R009C00, V200R010C00, S9700 V200R001C00, V200R001C01, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R006C01, V200R007C00, V200R007C01, V200R008C00, V200R009C00, V200R010C00 have an improper authorization vulnerability on Huawei switch products. The system incorrectly performs an authorization check when a normal user attempts to access certain information which is supposed to be accessed only by authenticated user. Successful exploit could cause information disclosure.

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

## Which versions are affected by CVE-2017-15327?

It affects 3 products.


Products: Huawei S12700 Firmware, Huawei S7700 Firmware, Huawei S9700 Firmware.

## How do I fix CVE-2017-15327?

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

## Is CVE-2017-15327 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. S12700, S7700, S9700

- [CVE-2016-4087](https://insights.sbomify.com/CVE-2016-4087/): Command injection in n/a (high 8.1)
- [CVE-2021-22357](https://insights.sbomify.com/CVE-2021-22357/): Denial of service in S12700;S5700;S6700;S7700 (high 7.5)
- [CVE-2019-19397](https://insights.sbomify.com/CVE-2019-19397/): Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700 (high 7.5)
- [CVE-2019-5285](https://insights.sbomify.com/CVE-2019-5285/): Denial of service in S12700, S12700, S12700, S12700, S12700, S12700, S12700, S12700, S1700, S1700, S1700, S1700, S1700, S1700, S2300, S2300, S2300, S2300, S2300, S2300, S2300, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S5300, S5300, S5300, S5300, S5300, S5300, S5300, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S600-E, S600-E, S600-E, S600-E, S600-E, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7900, S7900, S7900, S9300, S9300, S9300, S9300, S9300, S9300, S9300, S9300X, S9300X, S9300X, S9300X, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700 (high 7.5)
- [CVE-2016-8786](https://insights.sbomify.com/CVE-2016-8786/): Denial of service in S12700, S5700, S6700, S7700, S9700 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15327 and fix it if it is affected.

What it is: CVE-2017-15327 is a medium-severity missing authorization vulnerability in Huawei Technologies Co., Ltd. S12700, S7700, S9700, published on 11 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15327 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. S12700, S7700, S9700. 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-2017-15327/ (Markdown: https://insights.sbomify.com/CVE-2017-15327/index.md)
```

## Sources

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

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