CVE-2023-38298

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-04-22. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Various software builds for the following TCL devices (30Z, A3X, 20XE, 10L) leak the device IMEI to a system property that can be accessed by any local app on the device without any permissions or special privileges. Google restricted third-party apps from directly obtaining non-resettable device identifiers in Android 10 and higher, but in these instances they are leaked by a high-privilege process and can be obtained indirectly. The software build fingerprints for each confirmed vulnerable device are as follows: TCL 30Z (TCL/4188R/Jetta_ATT:12/SP1A.210812.016/LV8E:user/release-keys, TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU5P:user/release-keys, TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU61:user/release-keys, TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU66:user/release-keys, TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU68:user/release-keys, TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU6P:user/release-keys, and TCL/T602DL/Jetta_TF:12/SP1A.210812.016/vU6X:user/release-keys); TCL A3X (TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vAAZ:user/release-keys, TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vAB3:user/release-keys, TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vAB7:user/release-keys, TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vABA:user/release-keys, TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vABM:user/release-keys, TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vABP:user/release-keys, and TCL/A600DL/Delhi_TF:11/RKQ1.201202.002/vABS:user/release-keys); TCL 20XE (TCL/5087Z_BO/Doha_TMO:11/RP1A.200720.011/PB7I-0:user/release-keys and TCL/5087Z_BO/Doha_TMO:11/RP1A.200720.011/PB83-0:user/release-keys); and TCL 10L (TCL/T770B/T1_LITE:10/QKQ1.200329.002/3CJ0:user/release-keys and TCL/T770B/T1_LITE:11/RKQ1.210107.001/8BIC:user/release-keys). This malicious app reads from the "gsm.device.imei0" system property to indirectly obtain the device IMEI.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 22, 2024

Last Modified

April 15, 2026

References (2)

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-10-09 20:05 UTCEPSS rescore
  2. 2026-10-08 17:06 UTCEPSS rescore
  3. 2026-10-07 23:46 UTCEPSS rescore
  4. 2026-10-06 15:15 UTCEPSS rescore
  5. 2026-10-05 17:41 UTCEPSS rescore
  6. 2026-10-04 23:20 UTCEPSS rescore
  7. 2026-10-03 14:23 UTCEPSS rescore
  8. 2026-09-30 16:27 UTCEG score recompute
  9. 2026-09-30 15:01 UTCEPSS rescore
  10. 2026-09-29 15:16 UTCEPSS rescore
  11. 2026-09-28 13:49 UTCEPSS rescore
  12. 2026-09-27 13:42 UTCEPSS rescore
  13. 2026-09-26 15:55 UTCEPSS rescore
  14. 2026-09-26 00:22 UTCEPSS rescore
  15. 2026-09-24 14:01 UTCEPSS rescore
  16. 2026-09-24 14:01 UTCEPSS rescore
  17. 2026-09-23 13:45 UTCEPSS rescore
  18. 2026-09-22 14:45 UTCEPSS rescore
  19. 2026-09-16 14:05 UTCEPSS rescore
  20. 2026-09-13 16:44 UTCEPSS rescore
  21. 2026-09-12 14:58 UTCEPSS rescore
  22. 2026-09-11 14:50 UTCEPSS rescore
  23. 2026-09-11 09:34 UTCEPSS rescore
  24. 2026-09-08 21:57 UTCEPSS rescore
  25. 2026-09-07 15:59 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:45 UTCEPSS rescore
  2. 2026-09-05 15:26 UTCEPSS rescore
  3. 2026-09-04 13:58 UTCEPSS rescore
  4. 2026-09-04 05:04 UTCEPSS rescore
  5. 2026-09-02 14:09 UTCEPSS rescore
  6. 2026-09-01 13:51 UTCEPSS rescore
  7. 2026-08-30 19:15 UTCEPSS rescore
  8. 2026-08-30 01:20 UTCEPSS rescore
  9. 2026-08-28 21:38 UTCEPSS rescore
  10. 2026-08-27 14:23 UTCEPSS rescore
  11. 2026-08-26 14:43 UTCEPSS rescore
  12. 2026-08-25 13:46 UTCEPSS rescore
  13. 2026-08-24 14:14 UTCEPSS rescore
  14. 2026-08-23 00:17 UTCEPSS rescore
  15. 2026-08-21 23:47 UTCEPSS rescore
  16. 2026-08-20 22:53 UTCEPSS rescore
  17. 2026-08-19 17:02 UTCEPSS rescore
  18. 2026-08-18 13:46 UTCEPSS rescore
  19. 2026-08-17 13:45 UTCEPSS rescore
  20. 2026-08-16 14:54 UTCEPSS rescore
  21. 2026-08-16 02:12 UTCEPSS rescore
  22. 2026-08-15 01:28 UTCEPSS rescore
  23. 2026-08-13 21:58 UTCEPSS rescore
  24. 2026-08-12 13:48 UTCEPSS rescore
  25. 2026-08-11 13:39 UTCEPSS rescore
  26. 2026-08-09 13:44 UTCEPSS rescore
  27. 2026-08-08 16:34 UTCEPSS rescore
  28. 2026-08-07 16:24 UTCEPSS rescore
  29. 2026-08-06 13:44 UTCEPSS rescore
  30. 2026-08-05 19:15 UTCEPSS rescore
  31. 2026-08-05 19:15 UTCEPSS rescore
  32. 2026-08-04 15:07 UTCEPSS rescore
  33. 2026-08-04 10:35 UTCEPSS rescore
  34. 2026-08-03 10:34 UTCEPSS rescore
  35. 2026-08-02 02:25 UTCEPSS rescore
  36. 2026-08-01 04:13 UTCEPSS rescore
  37. 2026-07-30 16:26 UTCEPSS rescore
  38. 2026-07-30 16:26 UTCEPSS rescore
  39. 2026-07-30 01:28 UTCEPSS rescore
  40. 2026-07-30 01:28 UTCEPSS rescore
  41. 2026-07-28 15:34 UTCEPSS rescore
  42. 2026-07-27 14:10 UTCEPSS rescore
  43. 2026-07-26 14:52 UTCEPSS rescore
  44. 2026-07-25 14:16 UTCEPSS rescore
  45. 2026-07-24 14:16 UTCEPSS rescore
  46. 2026-07-23 14:16 UTCEPSS rescore
  47. 2026-07-23 14:16 UTCEPSS rescore
  48. 2026-07-23 02:25 UTCEG score recompute
  49. 2026-07-22 23:11 UTCEG score recompute
  50. 2026-07-22 14:06 UTCEPSS rescore
  51. 2026-07-21 15:23 UTCEPSS rescore
  52. 2026-07-21 15:23 UTCEPSS rescore
  53. 2026-07-20 17:06 UTCEPSS rescore
  54. 2026-07-19 14:29 UTCEPSS rescore
  55. 2026-07-19 14:29 UTCEPSS rescore
  56. 2026-07-19 02:27 UTCEPSS rescore
  57. 2026-07-19 02:27 UTCEPSS rescore
  58. 2026-07-18 10:03 UTCEPSS rescore
  59. 2026-07-18 10:03 UTCEPSS rescore
  60. 2026-07-16 17:01 UTCEPSS rescore
  61. 2026-07-15 16:56 UTCEPSS rescore
  62. 2026-07-15 16:56 UTCEPSS rescore
  63. 2026-07-15 01:58 UTCEPSS rescore
  64. 2026-07-15 01:58 UTCEPSS rescore
  65. 2026-07-13 22:28 UTCEPSS rescore
  66. 2026-07-13 22:28 UTCEPSS rescore
  67. 2026-07-13 06:11 UTCEPSS rescore
  68. 2026-07-13 06:11 UTCEPSS rescore
  69. 2026-07-12 05:45 UTCEPSS rescore
  70. 2026-07-11 08:26 UTCEPSS rescore
  71. 2026-07-11 08:25 UTCEPSS rescore
  72. 2026-07-09 19:08 UTCEPSS rescore
  73. 2026-07-09 19:08 UTCEPSS rescore
  74. 2026-07-08 15:13 UTCEPSS rescore
  75. 2026-07-07 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-38298?
CVE-2023-38298 is a high vulnerability published on April 22, 2024. Various software builds for the following TCL devices (30Z, A3X, 20XE, 10L) leak the device IMEI to a system property that can be accessed by any local app on the device without any permissions or special privileges. Google restricted third-party apps from directly obtaining non-resettable device…
When was CVE-2023-38298 disclosed?
CVE-2023-38298 was first published on April 22, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-38298 actively exploited?
CVE-2023-38298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-38298?
CVE-2023-38298 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2023-38298?
No fix for CVE-2023-38298 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-38298

Explore →

Is Your Infrastructure Affected by CVE-2023-38298?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs