dbcve.org
Ox 330p FirmwareOperating system · Zte

CVE-2015-7255

HIGH · 7.5 CVSS v3.0 Published 2017-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple ZTE router models (OX-330P, ZXHN H108N, W300V, HG110, GAN9.8T101A-B, MF28G) ship with non-unique X.509 certificates and SSH host keys that are identical across devices. This means multiple devices share the same cryptographic identity, defeating the purpose of certificate-based authentication and enabling man-in-the-middle attacks, passive decryption, or device impersonation.

MitigationGenerate and deploy unique X.509 certificates and SSH host keys for each device, either through firmware updates from the vendor or by accessing the administrative interface to replace default credentials. Consider disabling unused remote management services and implementing network segmentation for affected devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ox 330p FirmwareOperating system
Affected:all versions
Zxhn H108n FirmwareOperating system
Affected:all versions
W300v1.0.0s Zrd Tr1 D68 FirmwareOperating system
Affected:all versions
Hg110 FirmwareOperating system
Affected:all versions
Gan9.8t101a B FirmwareOperating system
Affected:all versions
Mf28g FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the device administrative interface or check the device label/marketing to determine the exact model number. Confirm it matches one of the affected models: OX-330P, ZXHN H108N, W300V, HG110, GAN9.8T101A-B, or MF28G.
    Affected if The device model is any of the affected ZTE models listed.
  2. Verify firmware version is not patched
    Check the device administrative interface for the firmware version. Since all versions are affected according to the advisory, any version confirms exposure.
    Affected if Any firmware version is installed on an affected model.
  3. Check if SSH service is enabled
    Attempt to connect to the device on port 22 (SSH) from the local network or via remote management. Use a tool like nmap or ssh to test connectivity: nc -zv <device_ip> 22 or ssh admin@<device_ip>
    Affected if SSH service is accessible and responds.
  4. Extract and compare SSH host keys
    Connect to the device via SSH and retrieve the host key fingerprint using: ssh-keyscan -t rsa,dsa,ecdsa <device_ip> 2>/dev/null. Repeat on a second device of the same model if available, or compare against publicly documented default key fingerprints for these models.
    Affected if The SSH host key matches the key from another device of the same model or matches a known default key.
  5. Retrieve and inspect X.509 certificates
    Access the device administrative web interface and navigate to the SSL/TLS or certificate settings page. Alternatively, if you have access to the device firmware image, extract and examine certificate files (.pem, .crt, .cer) from the firmware.
    Affected if The device uses a default certificate that is identical across multiple devices, or the certificate subject/issuer indicates a factory-default identity.

A user is affected if they operate any of the listed ZTE router models and the device uses default SSH host keys or X.509 certificates that are shared with other devices.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Generate and deploy unique X.509 certificates and SSH host keys for each device, either through firmware updates from the vendor or by accessing the administrative interface to replace default credentials. Consider disabling unused remote management services and implementing network segmentation for affected devices.

Fix this in Ox 330p Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation10.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7255 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-7255 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data