cnvd - cnvd-2019-32023

cnvd-2019-32023

Vulnerability from cnvd

Title: Telegram信息泄露漏洞（CNVD-2019-32023）

Description:

Telegram是一款即时通信移动应用程序。

基于Android平台的Telegram 5.11之前版本中存在信息泄露漏洞。该漏洞源于网络系统或产品在运行过程中存在配置等错误。未授权的攻击者可利用漏洞获取受影响组件敏感信息。

Severity: 中

Patch Name: Telegram信息泄露漏洞（CNVD-2019-32023）的补丁

Patch Description:

Telegram是一款即时通信移动应用程序。

基于Android平台的Telegram 5.11之前版本中存在信息泄露漏洞。该漏洞源于网络系统或产品在运行过程中存在配置等错误。未授权的攻击者可利用漏洞获取受影响组件敏感信息。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description:

目前厂商已发布升级补丁以修复漏洞，详情请关注厂商主页： https://telegram.org

Reference: https://nvd.nist.gov/vuln/detail/CVE-2019-16248

Impacted products

Name
Telegram Telegram <5.11

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-16248"
    }
  },
  "description": "Telegram\u662f\u4e00\u6b3e\u5373\u65f6\u901a\u4fe1\u79fb\u52a8\u5e94\u7528\u7a0b\u5e8f\u3002\n\n\u57fa\u4e8eAndroid\u5e73\u53f0\u7684Telegram 5.11\u4e4b\u524d\u7248\u672c\u4e2d\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u5728\u8fd0\u884c\u8fc7\u7a0b\u4e2d\u5b58\u5728\u914d\u7f6e\u7b49\u9519\u8bef\u3002\u672a\u6388\u6743\u7684\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u83b7\u53d6\u53d7\u5f71\u54cd\u7ec4\u4ef6\u654f\u611f\u4fe1\u606f\u3002",
  "discovererName": "unknwon",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8be6\u60c5\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\uff1a\r\nhttps://telegram.org",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-32023",
  "openTime": "2019-09-19",
  "patchDescription": "Telegram\u662f\u4e00\u6b3e\u5373\u65f6\u901a\u4fe1\u79fb\u52a8\u5e94\u7528\u7a0b\u5e8f\u3002\r\n\r\n\u57fa\u4e8eAndroid\u5e73\u53f0\u7684Telegram 5.11\u4e4b\u524d\u7248\u672c\u4e2d\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u5728\u8fd0\u884c\u8fc7\u7a0b\u4e2d\u5b58\u5728\u914d\u7f6e\u7b49\u9519\u8bef\u3002\u672a\u6388\u6743\u7684\u653b\u51fb\u8005\u53ef\u5229\u7528\u6f0f\u6d1e\u83b7\u53d6\u53d7\u5f71\u54cd\u7ec4\u4ef6\u654f\u611f\u4fe1\u606f\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Telegram\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-32023\uff09\u7684\u8865\u4e01",
  "products": {
    "product": "Telegram Telegram \u003c5.11"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2019-16248",
  "serverity": "\u4e2d",
  "submitTime": "2019-09-17",
  "title": "Telegram\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-32023\uff09"
}

CVE-2019-16248 (GCVE-0-2019-16248)

Vulnerability from cvelistv5

Published

2019-09-11 22:19

Modified

2024-08-05 01:10

Severity ?

CWE

Summary

The "delete for" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient's copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient's copy of a previously sent message).

References

▼	URL	Tags
	https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html	x_refsource_MISC
	https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf	x_refsource_MISC
	https://www.openwall.com/lists/oss-security/2019/09/09/2	x_refsource_MISC

Impacted products

	Vendor	Product	Version
	n/a	n/a	Version: n/a

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T01:10:41.671Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf"
          },
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://www.openwall.com/lists/oss-security/2019/09/09/2"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "The \"delete for\" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient\u0027s copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient\u0027s copy of a previously sent message)."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2019-09-11T22:19:49",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf"
        },
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://www.openwall.com/lists/oss-security/2019/09/09/2"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2019-16248",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "The \"delete for\" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient\u0027s copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient\u0027s copy of a previously sent message)."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html",
              "refsource": "MISC",
              "url": "https://www.inputzero.io/2019/09/telegram-privacy-fails-again.html"
            },
            {
              "name": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf",
              "refsource": "MISC",
              "url": "https://github.com/RootUp/PersonalStuff/blob/master/Telegram_Privacy.pdf"
            },
            {
              "name": "https://www.openwall.com/lists/oss-security/2019/09/09/2",
              "refsource": "MISC",
              "url": "https://www.openwall.com/lists/oss-security/2019/09/09/2"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2019-16248",
    "datePublished": "2019-09-11T22:19:49",
    "dateReserved": "2019-09-11T00:00:00",
    "dateUpdated": "2024-08-05T01:10:41.671Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
Confirmed: The vulnerability is confirmed from an analyst perspective.
Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
Patched: This vulnerability was successfully patched by the user reporting the sighting.
Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
Not confirmed: The user expresses doubt about the veracity of the vulnerability.
Not patched: This vulnerability was not successfully patched by the user reporting the sighting.

Action not permitted