CVE-2018-7366
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 · uneditedZTE ZXV10 B860AV2.1 product ChinaMobile branch with the ICNT versions up to V1.3.3, the BESTV versions up to V1.2.2, the WASU versions up to V1.1.7 and the MGTV versions up to V1.4.6 have an authentication bypass vulnerability, which may allows an unauthorized user to perform unauthorized operations.
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 confidenceZTE ZXV10 B860AV2.1 set-top box firmware contains an authentication bypass vulnerability across multiple carrier branch versions (ICNT up to V1.3.3, BESTV up to V1.2.2, WASU up to V1.1.7, MGTV up to V1.4.6). The flaw allows unauthorized users to bypass authentication controls and execute operations they should not have access to.
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< icnt_v1.3.3< bestv_v1.2.2< wasu_v1.1.7< mgtv_v1.4.6CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device label on the set-top box or access the device system information to confirm the model is ZTE ZXV10 B860AV2.1Affected if The device is not a ZTE ZXV10 B860AV2.1 model
-
Determine the carrier branch versionAccess the device firmware settings, system information page, or network service response to identify the carrier branch prefix (ICNT, BESTV, WASU, or MGTV) and the full version stringAffected if No carrier branch identifier (ICNT, BESTV, WASU, or MGTV) is found in the firmware version
-
Extract the numeric firmware versionParse the version string to isolate the numeric portion (for example, extract 1.3.3 from icnt_v1.3.3)Affected if The numeric version cannot be determined from the version string
-
Compare against vulnerable version thresholdsMatch the carrier branch to its threshold: ICNT version < 1.3.3, BESTV version < 1.2.2, WASU version < 1.1.7, or MGTV version < 1.4.6Affected if The installed version is less than the threshold for that specific carrier branch (for example, icnt_v1.3.2 or mgtv_v1.4.5)
-
Verify the authentication bypass conditionCheck if the device web interface, API endpoints, or management service can be accessed without credentials or with manipulated session tokensAffected if Unauthenticated or unauthorized access is possible on any management interface
The device is affected if it is a ZTE ZXV10 B860AV2.1 running any carrier branch version below the thresholds (ICNT < V1.3.3, BESTV < V1.2.2, WASU < V1.1.7, or MGTV < V1.4.6) and the device has its management interfaces exposed on the network.
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 dataApply vendor firmware updates beyond the vulnerable version thresholds for each carrier branch. If updates are unavailable, implement network segmentation and restrict device access to trusted networks only.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7366 — 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-2018-7366 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