Cross-site scripting via unsanitized document names
Published Jul 27, 2021 · Updated Aug 4, 2024
Cross-site scripting in Telegram Web K Alpha 0.6.1 allows remote attackers to execute script via a crafted document name. Document-processing paths pass the raw file_name value into message, audio, and document-title rendering rather than using the safe wrapped-text representation. Execution requires a recipient to render the malicious document name and exposes data and actions available to the web client.
Summary
What happened
Cross-site scripting in Telegram Web K Alpha 0.6.1 allows remote attackers to execute script via a crafted document name. Document-processing paths pass the raw file_name value into message, audio, and document-title rendering rather than using the safe wrapped-text representation. Execution requires a recipient to render the malicious document name and exposes data and actions available to the web client.
The record
- CVE
- CVE-2021-37596
- Published
- Jul 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 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