Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2019-5235

Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected…

Medium5.3EPSS 0.92%
Published
Updated
Reserved
Assigned by
huawei

Description

Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.

Scores

CVSS scores of CVE-2019-5235, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS (exploitation in 30 days)
0.92% · top 40% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.

Weakness

Affected products

  • Harry-AL00C, Harry-AL00C-PRELOAD, Harry-AL10B, Harry-LGRP1-CHN, Harry-TL00C, Jackman-AL00D, Jackman-L03, Jackman-L21, Jackman-L22, Jackman-L23, Johnson-AL00C, Johnson-AL00IC, Johnson-AL10C, Johnson-L21C, Johnson-L21D, Johnson-L22C, Johnson-L22D, Johnson-L23C, Johnson-L42IC, Johnson-L42IE, Johnson-L42IF, Johnson-TL00D, Johnson-TL00F, Potter-AL00C, Potter-AL10A, VOGUE-AL00A, VOGUE-AL00A-PRELOAD, VOGUE-AL10C, VOGUE-AL10C-PRELOAD, VOGUE-LGRP1-CHN, VOGUE-LGRP2-OVS, VOGUE-TL00B

    • affected Version
    • affected 9.1.0.206(C00E205R3P1)
    • affected 9.0.1.5(C735R1)
    • affected 9.1.0.1(C00R3)
    • affected 9.1.0.206
    • affected 9.0.1.162(C01E160R2P3)
    • affected 8.2.0.170(C861)
    • affected 8.2.0.188(C00R2P1)
    • affected 8.2.0.163(C605)
    • affected 8.2.0.160(C185)
    • affected 8.2.0.156(C636R2P2)
    • affected 8.2.0.152(C45CUSTC45D1)
    • affected 8.2.0.162(C605)
    • affected 8.2.0.175(C00R2P4)
    • affected 8.2.0.190(C788R1P16)
    • affected 8.2.0.161(C675CUSTC675D1)
    • affected 8.2.0.165(C00R1P16)
    • affected 8.2.0.130(C461R1P1)
    • affected 8.2.0.130(C652CUSTC652D1)
    • affected 8.2.0.131(C10R2P2)
    • affected 8.2.0.136(C432CUSTC432D1)
    • affected 8.2.0.101(C10CUSTC10D1)
    • affected 8.2.0.101(C432CUSTC432D1)
    • affected 8.2.0.131(C55CUSTC55D1)
    • affected 8.2.0.105(C185R1P1)
    • affected 8.2.0.107(C636R2P1)
    • affected 8.2.0.103(C652CUSTC652D1)
    • affected 8.2.0.105(C185R2P1)
    • affected 8.2.0.130(C636CUSTC636D2)
    • affected 8.2.0.133(C605CUSTC605D1)
    • affected 8.2.0.155(C675R2P1)
    • affected 8.2.0.110(C652CUSTC652D1)
    • affected 8.2.0.100(C541CUSTC541D1)
    • affected 8.2.0.165(C01R1P16)
    • affected 9.1.0.208(C00E205R3P1)
    • affected 9.1.0.162(C00E160R2P1)
    • affected 9.1.0.12(C00R1)
    • affected 9.1.0.4(C735R1)
    • affected 9.1.0.162
    • affected 9.1.0.161
    • and 1 more

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2019-5235 badge
[![CVE-2019-5235](https://trackcve.app/badge/CVE-2019-5235.svg)](https://trackcve.app/cve/CVE-2019-5235)

Record last updated .