Local device identifier disclosure via unprotected service
Published Jul 11, 2022 · Updated Aug 3, 2024
Information disclosure in SecSoterService on Samsung Mobile Devices Q(10), R(11), and S(12) allows local users to read a unique device ID. Samsung identifies improper use of the identifier in the unprotected service but does not disclose the affected API or code path. A locally running low-privilege application can obtain the identifier without user interaction; no integrity or availability impact is reported.
Summary
What happened
Information disclosure in SecSoterService on Samsung Mobile Devices Q(10), R(11), and S(12) allows local users to read a unique device ID. Samsung identifies improper use of the identifier in the unprotected service but does not disclose the affected API or code path. A locally running low-privilege application can obtain the identifier without user interaction; no integrity or availability impact is reported.
The record
- CVE
- CVE-2022-30753
- Published
- Jul 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-276, CWE-200, T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Q(10), R(11), S(12) <SMR Jul-2022 Release 1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo