CVE-2022-48383: High severity android vulnerability
Published May 9, 2023
·Updated
.In srtd service, there is a possible missing permission check. This could lead to local escalation of privilege with no additional execution privileges.
Affected Software
34 affected components
All of the following
Any of the following
Google Android=10.0
Google Android=11.0
Google Android=12.0
Google Android=13.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
Google Android=10.0
Google Android=11.0
Google Android=12.0
Google Android=13.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
Event History
May 9, 2023
CVE Published
via MITRE·01:21 AM
Data Sourced
via MITRE·01:21 AM
Description
Data Sourced
02:15 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2022-48383?
CVE-2022-48383 has a severity rating that could lead to local escalation of privilege due to a missing permission check.
2
How do I fix CVE-2022-48383?
To fix CVE-2022-48383, apply the latest security updates and patches provided by Google for affected Android versions.
3
Which versions of Android are affected by CVE-2022-48383?
CVE-2022-48383 affects Android versions 10.0, 11.0, 12.0, and 13.0.
4
What is the impact of CVE-2022-48383?
The impact of CVE-2022-48383 allows attackers to escalate privileges on the device without requiring additional permissions.
5
Are any Unisoc chips affected by CVE-2022-48383?
No, Unisoc chips such as S8000, SC7731E, SC9832E, and others are not vulnerable to CVE-2022-48383.