Image retention via failed self-destruction cleanup
Published Oct 4, 2021 · Updated Aug 4, 2024
Improper image deletion in Telegram for Android 7.5.0 through 7.8.0 allows local users to retain self-destructed images in shared storage. After roughly two to four uses of self-destruct, the interface reports deletion while image files remain in /Storage/Emulated/0/Telegram/Telegram Image/. Local access to the device storage is required, and the bounded consequence is failure to delete images that the interface represents as deleted.
Summary
What happened
Improper image deletion in Telegram for Android 7.5.0 through 7.8.0 allows local users to retain self-destructed images in shared storage. After roughly two to four uses of self-destruct, the interface reports deletion while image files remain in /Storage/Emulated/0/Telegram/Telegram Image/. Local access to the device storage is required, and the bounded consequence is failure to delete images that the interface represents as deleted.
The record
- CVE
- CVE-2021-41861
- Published
- Oct 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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