CVE-2019-5260
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 · uneditedHuawei smartphones HUAWEI Y9 2019 and Honor View 20 have a denial of service vulnerability. Due to insufficient input validation of specific value when parsing the messages, an attacker may send specially crafted TD-SCDMA messages from a rogue base station to the affected devices to exploit this vulnerability. Successful exploit may cause an infinite loop and the device to reboot.
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 confidenceThe Huawei Y9 2019 and Honor View 20 smartphones contain a vulnerability in their TD-SCDMA message parsing logic. Insufficient validation of specific values within TD-SCDMA messages received from a rogue base station causes an infinite loop, resulting in device reboot. An attacker with a malicious base station can trigger this denial of service condition remotely.
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= 8.2.0.160\(c185r2p2\)= 8.2.0.162\(c605\)= 8.2.0.163\(c605\)= 9.0.1.169\(c636e1r4p1\)= 9.0.1.170\(c185e2r3p1\)= 9.0.1.170\(c432e1r3p1\)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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify device modelCheck the device settings under Settings > About Phone > Model Name or use 'getprop ro.product.name' via ADB shellAffected if Device is not a Huawei Y9 2019 or Honor View 20 (also known as Honor V20 or View 20)
-
Check firmware build numberNavigate to Settings > About Phone > Build Number, or use 'getprop ro.build.display.id' via ADB shellAffected if Build number matches any of: 8.2.0.160(c185r2p2), 8.2.0.162(c605), 8.2.0.163(c605) for Y9 2019; or 9.0.1.169(c636e1r4p1), 9.0.1.170(c185e2r3p1), 9.0.1.170(c432e1r3p1) for Honor View 20
-
Verify TD-SCDMA network capabilityCheck if device supports TD-SCDMA by viewing mobile network settings or using 'getprop | grep td' via ADB shell to query TD-SCDMA related propertiesAffected if Device lacks TD-SCDMA support (less likely to be affected since the parsing logic exists but may not be exercised)
-
Confirm cellular radio/baseband versionAccess Settings > About Phone > Baseband version or use 'getprop gsm.version.baseband' via ADB shellAffected if Baseband version cannot be determined or device is running affected firmware versions listed above
Device is affected if it is a Huawei Y9 2019 or Honor View 20 running any of the specific firmware versions listed, as the vulnerable TD-SCDMA message parsing logic is present in those builds.
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-supplied firmware updates when available. Avoid connecting to untrusted or unknown cellular base stations as a workaround until patches are deployed.
- 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-2019-5260 — 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-2019-5260 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