Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| weebzone | Telegram-Stremio | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Weebzone | Telegram-stremio |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.110% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Weebzone
Weebzone telegram-stremio |
|
| Vendors & Products |
Weebzone
Weebzone telegram-stremio |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Telegram-Stremio through 5.1.0 contains an insecure storage vulnerability that allows attackers with access to the MongoDB database, backups, or logs to recover the operator's authenticated Telegram session string, which is protected only by a keyless, reversible encoding transform rather than actual encryption. Attackers can round-trip the stored value through the repository's own decode_string function with no secret key to obtain a fully authenticated Telegram session, granting complete control of the operator's Telegram account even when two-step verification is enabled. | |
| Title | Telegram-Stremio 5.1.0 Insecure Session Storage via encode_string | |
| Weaknesses | CWE-312 | |
| References |
| |
| Metrics |
cvssV3_1
|