# CVE-2015-7255: Weak cryptography in n/a

> Attackers can intercept credentials or impersonate devices via man-in-the-middle attacks due to non-unique X.509 certificates and SSH host keys.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 29 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v3q9-ph26-jhf2

## What is CVE-2015-7255?

CVE-2015-7255 is a high-severity vulnerability in n/a, published on 29 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZTE OX-330P, ZXHN H108N, W300V1.0.0S_ZRD_TR1_D68, HG110, GAN9.8T101A-B, MF28G, ZXHN H108N use non-unique X.509 certificates and SSH host keys, which might allow remote attackers to obtain credentials or other sensitive information via a man-in-the-middle attack, passive decryption attack, or impersonating a legitimate device.

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

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

It affects 6 products.


Products: Zte Gan9.8t101a-B Firmware, Zte Hg110 Firmware, Zte Mf28g Firmware, Zte Ox-330p Firmware, Zte W300v1.0.0s Zrd Tr1 D68 Firmware, Zte Zxhn H108n Firmware.

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

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

## Is CVE-2015-7255 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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