Telegram Messenger on iOS/Android Secret Message information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Telegram Messenger on iOS/Android and classified as problematic. This affects an unknown part of the component Secret Message Handler. This manipulation causes information disclosure. This vulnerability is handled as CVE-2014-8688. It is possible to launch the attack on the local host. There is not any exploit available.
Details
A vulnerability was found in Telegram Messenger on iOS/Android (Messaging Software). It has been declared as problematic. Affected by this vulnerability is an unknown part of the component Secret Message Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Telegram Messenger 2.6 for iOS and 1.8.2 for Android. Secret chat messages are available in cleartext in process memory and a .db file.
The bug was discovered 02/23/2015. The weakness was released 03/14/2017 (Website). It is possible to read the advisory at blog.zimperium.com. This vulnerability is known as CVE-2014-8688 since 11/09/2014. The exploitation appears to be difficult. Attacking locally is a requirement. A single authentication is necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 750 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Telegram Messenger auf iOS up to 2.6
- Telegram Messenger auf Android up to 1.8.2
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.5
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/09/2014 🔍02/23/2015 🔍
03/14/2017 🔍
03/14/2017 🔍
03/14/2017 🔍
09/06/2020 🔍
Sources
Advisory: blog.zimperium.comStatus: Not defined
CVE: CVE-2014-8688 (🔍)
GCVE (CVE): GCVE-0-2014-8688
GCVE (VulDB): GCVE-100-97891
OSVDB: - CVE-2014-8688 - Telegram Messenger - Information Disclosure Issue
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 03/14/2017 15:07Updated: 09/06/2020 12:07
Changes: 03/14/2017 15:07 (58), 09/06/2020 12:07 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.