User-triggered script execution via undisclosed content handling
Published Dec 6, 2022 · Updated Aug 3, 2024
Disputed cross-site scripting in Telegram Web 15.3.1 allows remote attackers to run script in a user's browser via the cited payload. The public report provides only a generic URL-processing shell pipeline and identifies no Telegram endpoint, code locus, or unsafe input-to-output operation. Execution requires user interaction, and the CVE record notes that third parties could not establish a relationship between the posted material and the claimed Telegram finding.
Summary
What happened
Disputed cross-site scripting in Telegram Web 15.3.1 allows remote attackers to run script in a user's browser via the cited payload. The public report provides only a generic URL-processing shell pipeline and identifies no Telegram endpoint, code locus, or unsafe input-to-output operation. Execution requires user interaction, and the CVE record notes that third parties could not establish a relationship between the posted material and the claimed Telegram finding.
The record
- CVE
- CVE-2022-43363
- Published
- Dec 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 6, 2022CVE 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.
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
- WAF bypass XSS Vulnerability in Telegramproof of concept · unverified
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