CVE-2019-2095: android Race Condition
CVSS: 7.6v2.0HighModified
Published 07-06-2019Last modified 04-08-2024
Vulnerability summary
CVE-2019-2095 is a high (CVSS 7.6) Race Condition vulnerability in android. EPSS estimates a 0.68% chance of exploitation in the next 30 days, higher than 51.4% of scored vulnerabilities.
CVSS score
7.6/10
010
High · v2.0 (NVD)EPSS score
0.68%
0%100%
Low · 0.00 pp in 30 daysKEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded
Timeline
- 07-06-2019PublishedVulnerability first disclosed.
- 04-08-2024Last modifiedVulnerability information updated.
Description
In callGenIDChangeListeners and related functions of SkPixelRef.cpp, there is a possible use after free due to a race condition. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: Android-9. Android ID: A-124232283.
CVSS metrics
2 scores · 1 source · 2 versionsHigh 7.0Preferred score · NVD (NIST)
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HSourcesSingle source
High 7.6Preferred score · NVD (NIST)
AV:N/AC:H/Au:N/C:C/I:C/A:CSourcesSingle source
EPSS trend
Probability
0.68%
Chance of exploitation in the next 30 days
Percentile
51%
Versus all other CVEs
30-day change
0.00 pp
From 0.68% on 20-09-2026
20-09-202620-10-2026
EPSS score0.68%
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
2 vendors · 2 products