How severe is CVE-2019-2173?

CVE-2019-2173 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-2173 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-2173?

CVE-2019-2173 primarily affects Google Android. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-2173?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-2173 published?

CVE-2019-2173 was published on 2019-10-11 and last updated on 2026-06-17.

CVE-2019-2173

CVE-2019-2173 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-276.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 4.6
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-276
Affected product: Google Android
Published: 2019-10-11
Last modified: 2026-06-17

Description

In startActivityMayWait of ActivityStarter.java, there is a possible incorrect Activity launch due to an incorrect permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9Android ID: A-123013720

Frequently asked questions

What is CVE-2019-2173?: In startActivityMayWait of ActivityStarter.java, there is a possible incorrect Activity launch due to an incorrect permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9Android ID: A-123013720
How severe is CVE-2019-2173?: CVE-2019-2173 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-2173 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-2173?: CVE-2019-2173 primarily affects Google Android. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-2173?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-2173 published?: CVE-2019-2173 was published on 2019-10-11 and last updated on 2026-06-17.

References

https://source.android.com/security/bulletin/2019-10-01

Affected products (5)

cpe:2.3:o:google:android:7.1.1:*:*:*:*:*:*:*
cpe:2.3:o:google:android:7.1.2:*:*:*:*:*:*:*
cpe:2.3:o:google:android:8.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:8.1:*:*:*:*:*:*:*
cpe:2.3:o:google:android:9.0:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-276 (Incorrect Default Permissions) vulnerabilities

CVE-2022-42150 — Critical (CVSS 10.0): TinyLab linux-lab v1.1-rc1 and cloud-labv0.8-rc2, v1.1-rc1 are vulnerable to insecure permissions. The default…
CVE-2020-29492 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2020-29491 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2025-40585 — Critical (CVSS 9.9): A vulnerability has been identified in Energy Services (All versions with G5DFR). Affected solutions using G5DFR…
CVE-2019-19896 — Critical (CVSS 9.9): In IXP EasyInstall 6.2.13723, there is Remote Code Execution via weak permissions on the Engine Service share. The…
CVE-2020-37129 — Critical (CVSS 9.8): Memu Play 7.1.3 contains an insecure folder permissions vulnerability that allows low-privileged users to modify the…

Browse all CWE-276 (Incorrect Default Permissions) vulnerabilities →