CNVD-2017-26624

Vulnerability from cnvd - Published: 2017-09-14
VLAI
Title
Cisco DPC3939和DPC3941T Comcast固件硬编码漏洞
Description
Cisco DPC3939和DPC3941T都是美国思科(Cisco)公司的无线语音网关产品。Comcast是一套运行在网关和调制解调器等设备中的美国康卡斯特(Comcast)公司开发的固件。 使用dpc3939-P20-18-v303r20421746-170221a-CMCST版本固件的Cisco DPC3939和使用DPC3941_2.5s3_PROD_sey版本固件的DPC3941T中的Comcast固件存在安全漏洞。远程攻击者可借助硬编码证书利用该漏洞访问Web UI。
Severity
中
Formal description

目前厂商暂未发布修复措施解决此安全问题,建议使用此软件的用户随时关注厂商主页或参考网址以获取解决办法: https://www.xfinity.com/

Reference
https://nvd.nist.gov/vuln/detail/CVE-2017-9488 https://github.com/BastilleResearch/CableTap/blob/master/doc/advisories/bastille-31.stb-remote-webui.txt
Impacted products
Name
['Cisco DPC3939 dpc3939-P20-18-v303r20421746-170221a-CMCST', 'Cisco DPC3941T DPC3941_2.5s3_PROD_sey']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-9488"
    }
  },
  "description": "Cisco DPC3939\u548cDPC3941T\u90fd\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u65e0\u7ebf\u8bed\u97f3\u7f51\u5173\u4ea7\u54c1\u3002Comcast\u662f\u4e00\u5957\u8fd0\u884c\u5728\u7f51\u5173\u548c\u8c03\u5236\u89e3\u8c03\u5668\u7b49\u8bbe\u5907\u4e2d\u7684\u7f8e\u56fd\u5eb7\u5361\u65af\u7279\uff08Comcast\uff09\u516c\u53f8\u5f00\u53d1\u7684\u56fa\u4ef6\u3002\r\n\r\n\u4f7f\u7528dpc3939-P20-18-v303r20421746-170221a-CMCST\u7248\u672c\u56fa\u4ef6\u7684Cisco DPC3939\u548c\u4f7f\u7528DPC3941_2.5s3_PROD_sey\u7248\u672c\u56fa\u4ef6\u7684DPC3941T\u4e2d\u7684Comcast\u56fa\u4ef6\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u501f\u52a9\u786c\u7f16\u7801\u8bc1\u4e66\u5229\u7528\u8be5\u6f0f\u6d1e\u8bbf\u95eeWeb UI\u3002",
  "discovererName": "unknow",
  "formalWay": "\u76ee\u524d\u5382\u5546\u6682\u672a\u53d1\u5e03\u4fee\u590d\u63aa\u65bd\u89e3\u51b3\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u5efa\u8bae\u4f7f\u7528\u6b64\u8f6f\u4ef6\u7684\u7528\u6237\u968f\u65f6\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u6216\u53c2\u8003\u7f51\u5740\u4ee5\u83b7\u53d6\u89e3\u51b3\u529e\u6cd5\uff1a\r\nhttps://www.xfinity.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-26624",
  "openTime": "2017-09-14",
  "products": {
    "product": [
      "Cisco DPC3939 dpc3939-P20-18-v303r20421746-170221a-CMCST",
      "Cisco DPC3941T DPC3941_2.5s3_PROD_sey"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2017-9488\r\nhttps://github.com/BastilleResearch/CableTap/blob/master/doc/advisories/bastille-31.stb-remote-webui.txt",
  "serverity": "\u4e2d",
  "submitTime": "2017-08-01",
  "title": "Cisco DPC3939\u548cDPC3941T Comcast\u56fa\u4ef6\u786c\u7f16\u7801\u6f0f\u6d1e"
}



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.