CVE-2023-25644
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 · uneditedThere is a denial of service vulnerability in some ZTE mobile internet products. Due to insufficient validation of Web interface parameter, an attacker could use the vulnerability to perform a denial of service attack.
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 confidenceA denial of service vulnerability exists in ZTE mobile internet products due to insufficient validation of Web interface parameters. An attacker can exploit this by sending specially crafted requests with malformed parameters to the Web interface, causing the service to become unavailable.
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= mc801a_elisa3_b19= mc801a1_elisa1_b04CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check device model identifierAccess the device's web administration interface (typically at 192.168.1.1 or 192.168.0.1) and navigate to System Settings or Device Information to view the model number. Confirm it is either ZTE Mc801a or ZTE Mc801a1.Affected if Device model is not Mc801a or Mc801a1
-
Locate firmware version informationIn the same web interface section (Device Information or Status), find the firmware version field. This is usually displayed as a text string showing the exact firmware build.Affected if Cannot locate firmware version in web interface
-
Compare installed firmware version against affected buildsRead the exact firmware version string displayed and compare it literally to: mc801a_elisa3_b19 or mc801a1_elisa1_b04. The version must match exactly (case-sensitive string comparison).Affected if Firmware version is exactly mc801a_elisa3_b19 OR mc801a1_elisa1_b04
-
Verify Web interface is accessibleConfirm the device Web management interface is currently reachable by attempting to load the login page in a browser. The vulnerability affects the Web interface component specifically.Affected if Web interface is not accessible or device is offline
You are affected only if your ZTE Mc801a or Mc801a1 device is running firmware version exactly mc801a_elisa3_b19 or mc801a1_elisa1_b04 respectively.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and sanitization for all Web interface parameters. This includes validating parameter types, lengths, and accepted character sets before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25644 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25644 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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