Local passcode disclosure via cleartext storage
Published Feb 12, 2021 · Updated Aug 3, 2024
Cleartext storage in Telegram Stable for macOS before 7.4 build 212543 allows local users to read the configured local passcode. The macOS client persists the local passcode without encryption, but public sources do not identify the backing file or preference key. Exploitation requires local access to the affected macOS account and reveals only the application passcode, with no reported message access or modification.
Summary
What happened
Cleartext storage in Telegram Stable for macOS before 7.4 build 212543 allows local users to read the configured local passcode. The macOS client persists the local passcode without encryption, but public sources do not identify the backing file or preference key. Exploitation requires local access to the affected macOS account and reveals only the application passcode, with no reported message access or modification.
The record
- CVE
- CVE-2021-27204
- Published
- Feb 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-312, T1552
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2021CVE 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?
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
- Telegram macOS local-passcode video proof of conceptproof of concept · demonstrated
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