dbcve.org
Up T2 4k FirmwareOperating system · Zte

CVE-2023-25645

HIGH · 7.7 CVSS v3.1 Published 2023-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
There is a permission and access control vulnerability in some ZTE AndroidTV STBs. Due to improper permission settings, non-privileged application can perform functions that are protected with signature/privilege-level permissions. Exploitation of this vulnerability could clear personal data and applications on the user's device, affecting device operation.

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 · moderate confidence

This is a privilege escalation vulnerability in ZTE AndroidTV Set-Top Boxes where improper permission configuration allows unprivileged applications to invoke functions protected by signature-level or higher privilege permissions. The vulnerability enables a malicious or compromised app to clear user data and installed applications, effectively causing data loss and disrupting device functionality.

MitigationApply vendor-provided firmware updates from ZTE that correct the permission settings; until patches are available, limit device network exposure and avoid installing untrusted third-party applications.

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
Up T2 4k FirmwareOperating system
Affected:= v84511302.1427
Zxv10 B866v2 H FirmwareOperating system
Affected:= v84711321.0038= v84711321.0040= v84711321.0045= v84711321.0049
Zxv10 B866v2 FirmwareOperating system
Affected:= v82811306.3021= v82815416.1027= v82815416.1028= v82815416.1029= v82815416.2012= v84711309.0016= v84711309.0018= v84711309.0019
Zxv10 B860h V5d0 FirmwareOperating system
Affected:= v83011303.0049= v83011303.0051= v83011303.0053= v83011303.0063= v83011303.0069
Zxv10 B866v2f FirmwareOperating system
Affected:= v86111338.0026= v86111338.0031= v86111338.0033= v86111338.0035

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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 device model
    Check the device settings or product label for the exact model name (e.g., Zte Up T2 4k, Zte Zxv10 B866v2 H, Zte Zxv10 B866v2, Zte Zxv10 B860h V5d0, Zte Zxv10 B866v2f)
    Affected if The device model is not one of these five affected models
  2. Retrieve the firmware version
    Access the device settings menu, typically under Settings > System > About Device or System Information, and note the firmware version number
    Affected if The firmware version cannot be retrieved or the device is not a ZTE AndroidTV Set-Top Box
  3. Compare firmware against affected versions for Up T2 4k
    If the device is Zte Up T2 4k, verify whether the firmware version equals exactly v84511302.1427
    Affected if Version equals v84511302.1427
  4. Compare firmware against affected versions for B866v2 H
    If the device is Zte Zxv10 B866v2 H, verify whether the firmware version equals any of: v84711321.0038, v84711321.0040, v84711321.0045, v84711321.0049
    Affected if Version matches any of the four listed versions
  5. Compare firmware against affected versions for B866v2
    If the device is Zte Zxv10 B866v2, verify whether the firmware version equals any of: v82811306.3021, v82815416.1027, v82815416.1028, v82815416.1029, v82815416.2012, v84711309.0016, v84711309.0018, v84711309.0019
    Affected if Version matches any of the eight listed versions
  6. Compare firmware against affected versions for B860h V5d0
    If the device is Zte Zxv10 B860h V5d0, verify whether the firmware version equals any of: v83011303.0049, v83011303.0051, v83011303.0053, v83011303.0063, v83011303.0069
    Affected if Version matches any of the five listed versions

The device is affected only if it is a ZTE AndroidTV Set-Top Box model from the five affected product lines AND its firmware version exactly matches one of the listed vulnerable versions for that model.

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

Apply vendor-provided firmware updates from ZTE that correct the permission settings; until patches are available, limit device network exposure and avoid installing untrusted third-party applications.

Fix this in Up T2 4k Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25645 — 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-2023-25645 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