CVE-2022-48384: 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-48384?
CVE-2022-48384 has been rated as a high severity vulnerability due to the potential for local escalation of privilege.
2
How do I fix CVE-2022-48384?
To mitigate CVE-2022-48384, ensure that your systems are updated with the latest security patches provided by Google for Android versions 10.0 to 13.0.
3
Which software versions are affected by CVE-2022-48384?
CVE-2022-48384 affects Google Android versions 10.0, 11.0, 12.0, and 13.0.
4
Can CVE-2022-48384 be exploited remotely?
CVE-2022-48384 cannot be exploited remotely as it requires local access to the affected device.
5
What kind of impact does CVE-2022-48384 pose?
CVE-2022-48384 may lead to unauthorized privilege escalation on vulnerable Android devices.