CVE-2019-5284
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 DoS vulnerability in RTSP module of Leland-AL00A Huawei smart phones versions earlier than Leland-AL00A 9.1.0.111(C00E111R2P10T8). Remote attackers could trick the user into opening a malformed RTSP media stream to exploit this vulnerability. Successful exploit could cause the affected phone abnormal, leading to a DoS condition. (Vulnerability ID: HWPSIRT-2019-02004)
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 confidenceThis is a denial-of-service vulnerability in the RTSP (Real Time Streaming Protocol) module of Huawei Leland-AL00A smartphones. The vulnerability exists in versions prior to 9.1.0.111(C00E111R2P10T8). Attackers exploit this by crafting a malformed RTSP media stream and tricking the user into opening it, which causes the phone to become unresponsive or abnormal.
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< leland-al00a_9.1.0.111\(c00e111r2p10t8\)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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify device modelCheck if the device is a Huawei Leland-AL00A smartphone. This can be done by going to Settings > About Phone > Model Number, or running 'getprop ro.product.model' via ADB or terminal emulator.Affected if The device model is not Huawei Leland-AL00A, then the device is not affected by this specific CVE.
-
Check firmware versionNavigate to Settings > About Phone > Version, or run 'getprop ro.build.version.emui' via ADB or terminal emulator to retrieve the EMUI firmware version.Affected if The firmware version is 9.1.0.111(C00E111R2P10T8) or higher, then the vulnerability is patched. If the version is lower than 9.1.0.111(C00E111R2P10T8), the device is within the affected range.
-
Identify RTSP usageCheck if the RTSP streaming protocol is used on the device. This can be verified by reviewing installed media player apps, surveillance camera apps, or streaming applications that may handle RTSP URLs. Look for apps that accept RTSP:// URLs as input.Affected if The device has applications that process RTSP streams and the firmware version is below 9.1.0.111(C00E111R2P10T8), the device is potentially vulnerable when opening untrusted RTSP content.
The device is affected if it is a Huawei Leland-AL00A with firmware version lower than 9.1.0.111(C00E111R2P10T8) and has apps or features that process RTSP media streams.
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 the vendor firmware update Leland-AL00A 9.1.0.111(C00E111R2P10T8) or later to affected devices. Users should be advised not to open untrusted RTSP media streams from unknown sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5284 — 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-5284 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