# CVE-2019-3428: Misconfiguration in ZXCDN IAMWEB

> An attacker can access the management portal via HTTP, leading to user information leakage due to a configuration error.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 22 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2285-87m3-9c89

## What is CVE-2019-3428?

CVE-2019-3428 is a medium-severity vulnerability in ZTE ZXCDN IAMWEB, published on 22 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The version V6.01.03.01 of ZTE ZXCDN IAMWEB product is impacted by a configuration error vulnerability. An attacker could directly access the management portal in HTTP, resulting in users’ information leakage.

## Which versions are affected by CVE-2019-3428?

It affects 1 product.


Products: Zte Zxcdn Iamweb Firmware.

## How do I fix CVE-2019-3428?

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

## Is CVE-2019-3428 being exploited?

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

## Other vulnerabilities in ZTE ZXCDN IAMWEB

- [CVE-2019-3427](https://insights.sbomify.com/CVE-2019-3427/): Code injection in ZXCDN IAMWEB (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3428 and fix it if it is affected.

What it is: CVE-2019-3428 is a medium-severity vulnerability in ZTE ZXCDN IAMWEB, published on 22 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3428 in the wild and no public exploit code.

Affected product: ZTE ZXCDN IAMWEB. 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-2019-3428/ (Markdown: https://insights.sbomify.com/CVE-2019-3428/index.md)
```

## Sources

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

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