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

> Remote attackers can read device configuration and enable PIN/PUK authentication on Huawei E5756S hotspots, exposing sensitive settings.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fwx9-f7r7-3g78

## What is CVE-2015-4629?

CVE-2015-4629 is a critical vulnerability in n/a, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Huawei E5756S before V200R002B146D23SP00C00 allows remote attackers to read device configuration information, enable PIN/PUK authentication, and perform other unspecified actions.

Weakness: CWE-264

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

It affects 1 product.


Products: Huawei E5756s Firmware.

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

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

## Is CVE-2015-4629 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4629 is a critical vulnerability in n/a, published on 7 Sep 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-4629 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-4629/ (Markdown: https://insights.sbomify.com/CVE-2015-4629/index.md)
```

## Sources

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

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