CVE-2022-39117: High severity android vulnerability
Published Oct 14, 2022
·Updated
In messaging service, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed.
Affected Software
32 affected components
Google Android=10.0
Google Android=11.0
Google Android=12.0
UNISOC S8000
UNISOC Sc7731e
UNISOC Sc9832e
UNISOC Sc9863a
UNISOC T310
UNISOC T606
UNISOC T610
UNISOC T612
UNISOC T616
UNISOC T618
UNISOC T760
UNISOC T770
UNISOC T820
All of the following
Any of the following
Google Android=10.0
Google Android=11.0
Google Android=12.0
Any of the following
UNISOC S8000
UNISOC Sc7731e
UNISOC Sc9832e
UNISOC Sc9863a
UNISOC T310
UNISOC T606
UNISOC T610
UNISOC T612
UNISOC T616
UNISOC T618
UNISOC T760
UNISOC T770
UNISOC T820
Event History
Oct 14, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-39117?
CVE-2022-39117 is categorized with a severity rating that allows local information disclosure due to a missing permission check.
2
How do I fix CVE-2022-39117?
To fix CVE-2022-39117, ensure that the messaging service includes the necessary permission checks to prevent unauthorized access.
3
Which versions of Android are affected by CVE-2022-39117?
CVE-2022-39117 affects Android versions 10.0, 11.0, and 12.0.
4
What type of vulnerability is CVE-2022-39117?
CVE-2022-39117 is a missing permission check vulnerability in the messaging service.
5
Can exploitation of CVE-2022-39117 occur without elevated privileges?
Yes, CVE-2022-39117 can be exploited with no additional execution privileges needed.