Message-rendering interruption via unsanitized document extensions
Published Sep 6, 2021 · Updated Aug 4, 2024
Improper input handling in Telegram Web K Alpha before 0.7.2 allows remote attackers to interrupt message rendering via a crafted filename. The wrapDocument function passed the unsanitized text after the final period to classList.add as an ext-prefixed DOM token, so spaces or other invalid characters raised an exception. Delivery of a document with such an extension triggers the failure; public evidence supports disrupted rendering but not code execution or data access.
Summary
What happened
Improper input handling in Telegram Web K Alpha before 0.7.2 allows remote attackers to interrupt message rendering via a crafted filename. The wrapDocument function passed the unsanitized text after the final period to classList.add as an ext-prefixed DOM token, so spaces or other invalid characters raised an exception. Delivery of a document with such an extension triggers the failure; public evidence supports disrupted rendering but not code execution or data access.
The record
- CVE
- CVE-2021-40532
- Published
- Sep 6, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 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