HTML Export XSS in Telegram Desktop
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Telegram | Telegram Desktop | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Telegram | Desktop |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.139% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTML Export XSS in Telegram Desktop |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Telegram desktop
|
|
| Vendors & Products |
Telegram desktop
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Telegram Desktop before 6.9.4 allows XSS in the HTML exporter. (The first fixed stable version is 7.0.1.) This occurs in button.text.toUtf8 in export_output_html.cpp. Exploitation cannot occur unless HTML export was used by a victim. However, the exploit payload can be exported if a message were forwarded into a group by a member (it is not necessary for the message author to be a member of a group). | |
| First Time appeared |
Telegram
Telegram telegram Desktop |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:telegram:telegram_desktop:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Telegram
Telegram telegram Desktop |
|
| References |
|
|
| Metrics |
cvssV3_1
|