CNVD-2019-13771

Vulnerability from cnvd - Published: 2019-05-10
VLAI
Title
多款Qualcomm产品信息泄露漏洞(CNVD-2019-13771)
Description
Qualcomm MDM9206等都是美国高通(Qualcomm)公司的产品。MDM9206是一款中央处理器(CPU)产品。Qualcomm MDM9150是一款中央处理器(CPU)产品。SDX20是一款调制解调器。 多款Qualcomm产品中存在信息泄露漏洞。该漏洞源于网络系统或产品在运行过程中存在配置等错误,未授权的攻击者可利用漏洞获取受影响组件敏感信息。
Severity
中
Patch Name
多款Qualcomm产品信息泄露漏洞(CNVD-2019-13771)的补丁
Patch Description
Qualcomm MDM9206等都是美国高通(Qualcomm)公司的产品。MDM9206是一款中央处理器(CPU)产品。Qualcomm MDM9150是一款中央处理器(CPU)产品。SDX20是一款调制解调器。 多款Qualcomm产品中存在信息泄露漏洞。该漏洞源于网络系统或产品在运行过程中存在配置等错误,未授权的攻击者可利用漏洞获取受影响组件敏感信息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://www.qualcomm.com/company/product-security/bulletins

Reference
https://vigilance.fr/vulnerability/Google-Android-multiple-vulnerabilities-of-May-2019-29239
Impacted products
Name
['Qualcomm SD 210', 'Qualcomm SD 212', 'Qualcomm SD 205', 'Qualcomm SD 845', 'Qualcomm SD 850', 'Qualcomm MDM9206', 'Qualcomm MDM9607', 'Qualcomm MSM8909W', 'Qualcomm MSM8996AU', 'Qualcomm SDX20', 'Qualcomm SD 425', 'Qualcomm SD 450', 'Qualcomm SD 615/16', 'Qualcomm SD 415', 'Qualcomm SD 625', 'Qualcomm SD 820', 'Qualcomm SD 820A', 'Qualcomm SD 835', 'Qualcomm SD 430', 'Qualcomm SD 410/12', 'Qualcomm SD 427', 'Qualcomm SD 435', 'Qualcomm SDM630', 'Qualcomm SDM660', 'Qualcomm Snapdragon_High_Med_2016', 'Qualcomm SDA660', 'Qualcomm SXR1130', 'Qualcomm MDM9635M', 'Qualcomm MDM9650', 'Qualcomm MDM9655', 'Qualcomm MDM9640', 'Qualcomm QCA8081', 'Qualcomm IPQ8074', 'Qualcomm SD 632', 'Qualcomm SD 8CX', 'Qualcomm SDM439', 'Qualcomm MDM9150', 'Qualcomm SD 439', 'Qualcomm SD 429', 'Qualcomm SD 636', 'Qualcomm SD 712', 'Qualcomm SD 710', 'Qualcomm SD 670', 'Qualcomm SD 855', 'Qualcomm Qualcomm 215', 'Qualcomm IPQ4019', 'Qualcomm QCS405', 'Qualcomm QCS605', 'Qualcomm SD 650/52']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-13906"
    }
  },
  "description": "Qualcomm MDM9206\u7b49\u90fd\u662f\u7f8e\u56fd\u9ad8\u901a\uff08Qualcomm\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002MDM9206\u662f\u4e00\u6b3e\u4e2d\u592e\u5904\u7406\u5668\uff08CPU\uff09\u4ea7\u54c1\u3002Qualcomm MDM9150\u662f\u4e00\u6b3e\u4e2d\u592e\u5904\u7406\u5668\uff08CPU\uff09\u4ea7\u54c1\u3002SDX20\u662f\u4e00\u6b3e\u8c03\u5236\u89e3\u8c03\u5668\u3002\n\n\u591a\u6b3eQualcomm\u4ea7\u54c1\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\uff0c\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": "unknown",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://www.qualcomm.com/company/product-security/bulletins",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-13771",
  "openTime": "2019-05-10",
  "patchDescription": "Qualcomm MDM9206\u7b49\u90fd\u662f\u7f8e\u56fd\u9ad8\u901a\uff08Qualcomm\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002MDM9206\u662f\u4e00\u6b3e\u4e2d\u592e\u5904\u7406\u5668\uff08CPU\uff09\u4ea7\u54c1\u3002Qualcomm MDM9150\u662f\u4e00\u6b3e\u4e2d\u592e\u5904\u7406\u5668\uff08CPU\uff09\u4ea7\u54c1\u3002SDX20\u662f\u4e00\u6b3e\u8c03\u5236\u89e3\u8c03\u5668\u3002\r\n\r\n\u591a\u6b3eQualcomm\u4ea7\u54c1\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\uff0c\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": "\u591a\u6b3eQualcomm\u4ea7\u54c1\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-13771\uff09\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Qualcomm SD 210",
      "Qualcomm SD 212",
      "Qualcomm SD 205",
      "Qualcomm SD 845",
      "Qualcomm SD 850",
      "Qualcomm MDM9206",
      "Qualcomm MDM9607",
      "Qualcomm MSM8909W",
      "Qualcomm MSM8996AU",
      "Qualcomm SDX20",
      "Qualcomm SD 425",
      "Qualcomm SD 450",
      "Qualcomm SD 615/16",
      "Qualcomm SD 415",
      "Qualcomm SD 625",
      "Qualcomm SD 820",
      "Qualcomm SD 820A",
      "Qualcomm SD 835",
      "Qualcomm SD 430",
      "Qualcomm SD 410/12",
      "Qualcomm SD 427",
      "Qualcomm SD 435",
      "Qualcomm SDM630",
      "Qualcomm SDM660",
      "Qualcomm Snapdragon_High_Med_2016",
      "Qualcomm SDA660",
      "Qualcomm SXR1130",
      "Qualcomm MDM9635M",
      "Qualcomm MDM9650",
      "Qualcomm MDM9655",
      "Qualcomm MDM9640",
      "Qualcomm QCA8081",
      "Qualcomm IPQ8074",
      "Qualcomm SD 632",
      "Qualcomm SD 8CX",
      "Qualcomm SDM439",
      "Qualcomm MDM9150",
      "Qualcomm SD 439",
      "Qualcomm SD 429",
      "Qualcomm SD 636",
      "Qualcomm SD 712",
      "Qualcomm SD 710",
      "Qualcomm SD 670",
      "Qualcomm SD 855",
      "Qualcomm Qualcomm 215",
      "Qualcomm IPQ4019",
      "Qualcomm QCS405",
      "Qualcomm QCS605",
      "Qualcomm SD 650/52"
    ]
  },
  "referenceLink": "https://vigilance.fr/vulnerability/Google-Android-multiple-vulnerabilities-of-May-2019-29239",
  "serverity": "\u4e2d",
  "submitTime": "2019-05-09",
  "title": "\u591a\u6b3eQualcomm\u4ea7\u54c1\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-13771\uff09"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.