What is the severity of CVE-2022-33688?

CVE-2022-33688 is rated as a medium severity vulnerability due to its potential to expose sensitive information.

How do I fix CVE-2022-33688?

To mitigate CVE-2022-33688, users should update to the latest security patch provided by their device manufacturer.

Who is affected by CVE-2022-33688?

CVE-2022-33688 affects devices running Android versions 10.0, 11.0, and 12.0.

What type of vulnerability is CVE-2022-33688?

CVE-2022-33688 is classified as a sensitive information exposure vulnerability in the SecTelephonyProvider.

How can local attackers exploit CVE-2022-33688?

Local attackers can exploit CVE-2022-33688 by accessing device logs to retrieve the IMSI, given they have log access permissions.

Vulnerability/
CVE-2022-33688

low

3.3

CWE

532

11/7/2022

3/8/2024

CVE-2022-33688

First published: Mon Jul 11 2022(Updated: )

Sensitive information exposure vulnerability in EventType in SecTelephonyProvider prior to SMR Jul-2022 Release 1 allows local attackers with log access permission to get IMSI through device log.

Credit: mobile.security@samsung.com

Affected Software	Affected Version	How to fix
Google Android	=10.0
Google Android	=11.0
Google Android	=12.0

Never miss a vulnerability like this again

Reference Links

https://security.samsungmobile.com/securityUpdate.smsb?year=2022&month=7

Frequently Asked Questions

What is the severity of CVE-2022-33688?
CVE-2022-33688 is rated as a medium severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2022-33688?
To mitigate CVE-2022-33688, users should update to the latest security patch provided by their device manufacturer.
Who is affected by CVE-2022-33688?
CVE-2022-33688 affects devices running Android versions 10.0, 11.0, and 12.0.
What type of vulnerability is CVE-2022-33688?
CVE-2022-33688 is classified as a sensitive information exposure vulnerability in the SecTelephonyProvider.
How can local attackers exploit CVE-2022-33688?
Local attackers can exploit CVE-2022-33688 by accessing device logs to retrieve the IMSI, given they have log access permissions.

agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/weakness
agent/author
agent/references
agent/description
agent/event
agent/first-publish-date
agent/tags
agent/source
vendor/google
canonical/google android
version/google android/10.0
version/google android/11.0
version/google android/12.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-33688?
CVE-2022-33688 is rated as a medium severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2022-33688?
To mitigate CVE-2022-33688, users should update to the latest security patch provided by their device manufacturer.
Who is affected by CVE-2022-33688?
CVE-2022-33688 affects devices running Android versions 10.0, 11.0, and 12.0.
What type of vulnerability is CVE-2022-33688?
CVE-2022-33688 is classified as a sensitive information exposure vulnerability in the SecTelephonyProvider.
How can local attackers exploit CVE-2022-33688?
Local attackers can exploit CVE-2022-33688 by accessing device logs to retrieve the IMSI, given they have log access permissions.