CVE-2022-30753: Infoleak
First published: Mon Jul 11 2022(Updated: )
Improper use of a unique device ID in unprotected SecSoterService prior to SMR Jul-2022 Release 1 allows local attackers to get the device ID without permission.
Credit: mobile.security@samsung.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Android | =10.0 | |
| Android | =11.0 | |
| Android | =12.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2022-30753?
CVE-2022-30753 has a high severity rating due to its potential to allow local attackers to access sensitive device information.
How do I fix CVE-2022-30753?
To fix CVE-2022-30753, ensure your device is updated to the latest security patch provided by Google for Android versions 10.0, 11.0, or 12.0.
Who is affected by CVE-2022-30753?
Devices running Android versions 10.0, 11.0, and 12.0 are affected by CVE-2022-30753.
What kind of attacks can exploit CVE-2022-30753?
CVE-2022-30753 can be exploited by local attackers who can gain unauthorized access to a unique device ID.
Is there a workaround for CVE-2022-30753?
Currently, the best workaround for CVE-2022-30753 is to apply the relevant security updates from Google.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/author
- agent/references
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/android
- version/android/10.0
- version/android/11.0
- version/android/12.0