What is CVE-2019-5303?A medium-severity flaw in Alp-Al00b, explained.
CVE-2019-5303 is a medium-severity flaw (CVSS 5.3) in Alp-Al00b from Huawei, published on 27 April 2020. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.3%. If you run an affected version, plan in the vendor’s fix.
Published 27 April 2020. Record last updated 5 May 2020. We keep this page's data up to date.
What is CVE-2019-5303? In plain terms.
An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
There are two denial of service vulnerabilities on some Huawei smartphones. An attacker may send specially crafted TD-SCDMA messages from a rogue base station to the affected devices. Due to insufficient input validation of two values when parsing the messages, successful exploit may cause device abnormal. This is 2 out of 2 vulnerabilities. Different than CVE-2020-5302. Affected products are: ALP-AL00B: earlier than 9.1.0.333(C00E333R2P1T8) ALP-L09: earlier than 9.1.0.300(C432E4R1P9T8) ALP-L29: earlier than 9.1.0.315(C636E5R1P13T8) BLA-L29C: earlier than 9.1.0.321(C636E4R1P14T8), earlier than 9.1.0.330(C432E6R1P12T8), earlier than 9.1.0.302(C635E4R1P13T8) Berkeley-AL20: earlier than 9.1.0.333(C00E333R2P1T8) Berkeley-L09: earlier than 9.1.0.350(C10E3R1P14T8), earlier than 9.1.0.351(C432E5R1P13T8), earlier than 9.1.0.350(C636E4R1P13T8) Charlotte-L09C: earlier than 9.1.0.311(C185E4R1P11T8), earlier than 9.1.0.345(C432E8R1P11T8) Charlotte-L29C: earlier than 9.1.0.325(C185E4R1P11T8), earlier than 9.1.0.335(C636E3R1P13T8), earlier than 9.1.0.345(C432E8R1P11T8), earlier than 9.1.0.336(C605E3R1P12T8) Columbia-AL10B: earlier than 9.1.0.333(C00E333R1P1T8) Columbia-L29D: earlier than 9.1.0.350(C461E3R1P11T8), earlier than 9.1.0.350(C185E3R1P12T8), earlier than 9.1.0.350(C10E5R1P14T8), earlier than 9.1.0.351(C432E5R1P13T8) Cornell-AL00A: earlier than 9.1.0.333(C00E333R1P1T8) Cornell-L29A: earlier than 9.1.0.328(C185E1R1P9T8), earlier than 9.1.0.328(C432E1R1P9T8), earlier than 9.1.0.330(C461E1R1P9T8), earlier than 9.1.0.328(C636E2R1P12T8) Emily-L09C: earlier than 9.1.0.336(C605E4R1P12T8), earlier than 9.1.0.311(C185E2R1P12T8), earlier than 9.1.0.345(C432E10R1P12T8) Emily-L29C: earlier than 9.1.0.311(C605E2R1P12T8), earlier than 9.1.0.311(C636E7R1P13T8), earlier than 9.1.0.311(C432E7R1P11T8) Ever-L29B: earlier than 9.1.0.311(C185E3R3P1), earlier than 9.1.0.310(C636E3R2P1), earlier than 9.1.0.310(C432E3R1P12) HUAWEI Mate 20: earlier than 9.1.0.131(C00E131R3P1) HUAWEI Mate 20 Pro: earlier than 9.1.0.310(C185E10R2P1) HUAWEI Mate 20 RS: earlier than 9.1.0.135(C786E133R3P1) HUAWEI Mate 20 X: earlier than 9.1.0.135(C00E133R2P1) HUAWEI P20: earlier than 9.1.0.333(C00E333R1P1T8) HUAWEI P20 Pro: earlier than 9.1.0.333(C00E333R1P1T8) HUAWEI P30: earlier than 9.1.0.193 HUAWEI P30 Pro: earlier than 9.1.0.186(C00E180R2P1) HUAWEI Y9 2019: earlier than 9.1.0.220(C605E3R1P1T8) HUAWEI nova lite 3: earlier than 9.1.0.305(C635E8R2P2) Honor 10 Lite: earlier than 9.1.0.283(C605E8R2P2) Honor 8X: earlier than 9.1.0.221(C461E2R1P1T8) Honor View 20: earlier than 9.1.0.238(C432E1R3P1) Jackman-L22: earlier than 9.1.0.247(C636E2R4P1T8) Paris-L21B: earlier than 9.1.0.331(C432E1R1P2T8) Paris-L21MEB: earlier than 9.1.0.331(C185E4R1P3T8) Paris-L29B: earlier than 9.1.0.331(C636E1R1P3T8) Sydney-AL00: earlier than 9.1.0.212(C00E62R1P7T8) Sydney-L21: earlier than 9.1.0.215(C432E1R1P1T8), earlier than 9.1.0.213(C185E1R1P1T8) Sydney-L21BR: earlier than 9.1.0.213(C185E1R1P2T8) Sydney-L22: earlier than 9.1.0.258(C636E1R1P1T8) Sydney-L22BR: earlier than 9.1.0.258(C636E1R1P1T8) SydneyM-AL00: earlier than 9.1.0.228(C00E78R1P7T8) SydneyM-L01: earlier than 9.1.0.215(C782E2R1P1T8), earlier than 9.1.0.213(C185E1R1P1T8), earlier than 9.1.0.270(C432E3R1P1T8) SydneyM-L03: earlier than 9.1.0.217(C605E1R1P1T8) SydneyM-L21: earlier than 9.1.0.221(C461E1R1P1T8), earlier than 9.1.0.215(C432E4R1P1T8) SydneyM-L22: earlier than 9.1.0.259(C185E1R1P2T8), earlier than 9.1.0.220(C635E1R1P2T8), earlier than 9.1.0.216(C569E1R1P1T8) SydneyM-L23: earlier than 9.1.0.226(C605E2R1P1T8) Yale-L21A: earlier than 9.1.0.154(C432E2R3P2), earlier than 9.1.0.154(C461E2R2P1), earlier than 9.1.0.154(C636E2R2P1) Honor 20: earlier than 9.1.0.152(C00E150R5P1) Honor Magic2: earlier than 10.0.0.187 Honor V20: earlier than 9.1.0.234(C00E234R4P3)
What kind of flaw is it?
- CWE-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2019-5303 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2019-5303 scores 16. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-5303 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-5303? 94 products.
The published record lists 94 products from 1 vendor. Versions are shown as published: "before 9.1.0.325(c185e4r1p11t8)" means every version up to, but not including, 9.1.0.325(c185e4r1p11t8). If you run one of these, check your version, then go to the fix below.
- Hardware
Alp-Al00b
by Huawei
Affected versionsversion not specified - Operating system
Charlotte-L29c Firmware
by Huawei
Affected versionsbefore 9.1.0.325(c185e4r1p11t8)before 9.1.0.335(c636e3r1p13t8)before 9.1.0.345(c432e8r1p11t8)before 9.1.0.336(c605e3r1p12t8) - Operating system
Columbia-L29d Firmware
by Huawei
Affected versionsbefore 9.1.0.350(c461e3r1p11t8)before 9.1.0.350(c185e3r1p12t8)before 9.1.0.350(c10e5r1p14t8)before 9.1.0.351(c432e5r1p13t8) - Operating system
Cornell-L29a Firmware
by Huawei
Affected versionsbefore 9.1.0.328(c185e1r1p9t8)before 9.1.0.328(c432e1r1p9t8)before 9.1.0.330(c461e1r1p9t8)before 9.1.0.328(c636e2r1p12t8) - Operating system
Berkeley-L09 Firmware
by Huawei
Affected versionsbefore 9.1.0.350(c10e3r1p14t8)before 9.1.0.351(c432e5r1p13t8)before 9.1.0.350(c636e4r1p13t8) - Operating system
Bla-L29c Firmware
by Huawei
Affected versionsbefore 9.1.0.321(c636e4r1p14t8)before 9.1.0.330(c432e6r1p12t8)before 9.1.0.302(c635e4r1p13t8) - Operating system
Emily-L09c Firmware
by Huawei
Affected versionsbefore 9.1.0.336(c605e4r1p12t8)before 9.1.0.311(c185e2r1p12t8)before 9.1.0.345(c432e10r1p12t8) - Operating system
Emily-L29c Firmware
by Huawei
Affected versionsbefore 9.1.0.311(c605e2r1p12t8)before 9.1.0.311(c636e7r1p13t8)before 9.1.0.311(c432e7r1p11t8) - Operating system
Ever-L29b Firmware
by Huawei
Affected versionsbefore 9.1.0.311(c185e3r3p1)before 9.1.0.310(c636e3r2p1)before 9.1.0.310(c432e3r1p12)
How do I fix CVE-2019-5303? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
1 linkDoes CVE-2019-5303 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
There are two denial of service vulnerabilities on some Huawei smartphones. An attacker may send specially crafted TD-SCDMA messages from a rogue base statio...
- Matched to
- Alp-Al00b on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-5303 is a medium-severity flaw in Alp-Al00b from Huawei, published on 27 April 2020. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 5.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2019-5303 is 16 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.3%. That can change at any time, which is why we keep watching.
For Alp-Al00b from Huawei: version not specified. The record lists 94 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.