CVE-2022-38697: Medium severity android vulnerability

Published Oct 14, 2022

Updated

In messaging service, there is a missing permission check. This could lead to access unexpected provider in contacts service 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

Frequently Asked Questions

What is the severity of CVE-2022-38697?

The severity of CVE-2022-38697 is categorized as medium due to the potential for unauthorized access to contact information.

How does CVE-2022-38697 affect Android devices?

CVE-2022-38697 affects Android devices running versions 10.0, 11.0, and 12.0, due to a missing permission check in the messaging service.

How do I fix CVE-2022-38697?

To fix CVE-2022-38697, ensure that your Android device is updated to the latest version provided by your manufacturer.

Can CVE-2022-38697 allow access to sensitive contacts?

Yes, CVE-2022-38697 can potentially allow unauthorized access to sensitive contacts stored on the device.

Are all Unisoc devices vulnerable to CVE-2022-38697?

No, Unisoc devices like S8000, SC7731, and others do not exhibit vulnerability to CVE-2022-38697.