# CVE-2018-7356: Other in ZXR10 8905E

> Remote attackers can spoof connections on ZTE ZXR10 switches due to predictable TCP Initial Sequence Numbers, bypassing authentication mechanisms.

- **Severity:** Medium 5.6 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7j79-33fw-38v7

## What is CVE-2018-7356?

CVE-2018-7356 is a medium-severity vulnerability in ZTE ZXR10 8905E, published on 1 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions up to V3.03.10.B23P2 of ZTE ZXR10 8905E product are impacted by TCP Initial Sequence Number (ISN) reuse vulnerability, which can generate easily predictable ISN, and allows remote attackers to spoof connections.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2018-7356?

It affects 1 product.


Products: Zte Zxr10 8905e Firmware.

## How do I fix CVE-2018-7356?

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

## Is CVE-2018-7356 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7356 and fix it if it is affected.

What it is: CVE-2018-7356 is a medium-severity vulnerability in ZTE ZXR10 8905E, published on 1 Nov 2018. 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-2018-7356 in the wild and no public exploit code.

Affected product: ZTE ZXR10 8905E. 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-2018-7356/ (Markdown: https://insights.sbomify.com/CVE-2018-7356/index.md)
```

## Sources

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

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