SQL injection via MemorySaver Content Provider
Published Mar 24, 2020 · Updated Aug 5, 2024
SQL injection in Samsung mobile devices with P(9.0) software allows attackers to manipulate MemorySaver Content Provider queries via unspecified vectors. The record identifies the MemorySaver Content Provider as the vulnerable locus but does not disclose the specific query or input-handling flaw. Required permissions and reachable interface are not specified, and impact beyond SQL query manipulation is not documented.
Summary
What happened
SQL injection in Samsung mobile devices with P(9.0) software allows attackers to manipulate MemorySaver Content Provider queries via unspecified vectors. The record identifies the MemorySaver Content Provider as the vulnerable locus but does not disclose the specific query or input-handling flaw. Required permissions and reachable interface are not specified, and impact beyond SQL query manipulation is not documented.
The record
- CVE
- CVE-2019-20576
- Published
- Mar 24, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89
- Attack vector
- Unavailable
- Privileges
- Unavailable
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
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