Memory corruption via tlc_server heap overflow
Published Apr 7, 2020 · Updated Aug 6, 2024
A heap-based buffer overflow in tlc_server on Samsung mobile devices running Android 6.0 allows remote attackers to corrupt process memory. Public records identify the tlc_server heap as the locus but do not disclose the input, allocation, or write operation that overruns it. Network reachability without prior privileges is sufficient to reach the flaw, but published material does not establish whether exploitation produces code execution, a crash, or another concrete outcome.
Summary
What happened
A heap-based buffer overflow in tlc_server on Samsung mobile devices running Android 6.0 allows remote attackers to corrupt process memory. Public records identify the tlc_server heap as the locus but do not disclose the input, allocation, or write operation that overruns it. Network reachability without prior privileges is sufficient to reach the flaw, but published material does not establish whether exploitation produces code execution, a crash, or another concrete outcome.
The record
- CVE
- CVE-2016-11033
- Published
- Apr 7, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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.
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