CVE-2017-5217

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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

Installing a zero-permission Android application on certain Samsung Android devices with KK(4.4), L(5.0/5.1), and M(6.0) software can continually crash the system_server process in the Android OS. The zero-permission app will create an active install session for a separate app that it has embedded within it. The active install session of the embedded app is performed using the android.content.pm.PackageInstaller class and its nested classes in the Android API. The active install session will write the embedded APK file to the /data/app directory, but the app will not be installed since third-party applications cannot programmatically install apps. Samsung has modified AOSP in order to accelerate the parsing of APKs by introducing the com.android.server.pm.PackagePrefetcher class and its nested classes. These classes will parse the APKs present in the /data/app directory and other directories, even if the app is not actually installed. The embedded APK that was written to the /data/app directory via the active install session has a very large but valid AndroidManifest.xml file. Specifically, the AndroidManifest.xml file contains a very large string value for the name of a permission-tree that it declares. When system_server tries to parse the APK file of the embedded app from the active install session, it will crash due to an uncaught error (i.e., java.lang.OutOfMemoryError) or an uncaught exception (i.e., std::bad_alloc) because of memory constraints. The Samsung Android device will encounter a soft reboot due to a system_server crash, and this action will keep repeating since parsing the APKs in the /data/app directory as performed by the system_server process is part of the normal boot process. The Samsung ID is SVE-2016-6917.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
30
EG Risk 30/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
Severity55% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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.8%
EPSS %ILE
55th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

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 none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

January 9, 2017

Last Modified

June 17, 2026

References (4)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 19× 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 145 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-5217?
CVE-2017-5217 is a medium vulnerability published on January 9, 2017. Installing a zero-permission Android application on certain Samsung Android devices with KK(4.4), L(5.0/5.1), and M(6.0) software can continually crash the systemserver process in the Android OS. The zero-permission app will create an active install session for a separate app that it has embedded…
When was CVE-2017-5217 disclosed?
CVE-2017-5217 was first published on January 9, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5217 actively exploited?
CVE-2017-5217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-5217?
CVE-2017-5217 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2017-5217?
No fix for CVE-2017-5217 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-2017-5217

Explore →

Is Your Infrastructure Affected by CVE-2017-5217?

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

Book a Demo →Browse All CVEs