IMEI manipulation via undisclosed protection flaw
Published Mar 24, 2020 · Updated Aug 5, 2024
Improper IMEI protection in Samsung Galaxy S9 and Note9 devices before October 2019 allows attackers to alter the device identifier. Samsung states only that the IMEI security mechanism requires enhancement and has not disclosed the affected component or the operation that accepts untrusted input. The public record does not identify the required access path or any prerequisite, while the bounded consequence is modification of the handset's IMEI.
Summary
What happened
Improper IMEI protection in Samsung Galaxy S9 and Note9 devices before October 2019 allows attackers to alter the device identifier. Samsung states only that the IMEI security mechanism requires enhancement and has not disclosed the affected component or the operation that accepts untrusted input. The public record does not identify the required access path or any prerequisite, while the bounded consequence is modification of the handset's IMEI.
The record
- CVE
- CVE-2019-20564
- Published
- Mar 24, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No sourced classifications are available.
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