CNVD-2017-36397

Vulnerability from cnvd - Published: 2017-12-06
VLAI
Title
Cisco IP Phone 8800 Series设备拒绝服务漏洞
Description
Cisco IP Phone 8800 Series devices是美国思科(Cisco)公司的一款提供视频和VoIP通信功能的IP电话。Session Initiation Protocol(SIP)是使用在其中的一个会话启动协议。 Cisco IP Phone 8800 Series设备中的Session Initiation Protocol (SIP)调用的处理存在拒绝服务漏洞,该漏洞源于程序未能对SIP数据包包头执行充分的输入验证。远程攻击者可通过向目标电话发送畸形的SIP数据包利用该漏洞造成拒绝服务(SIP进程重启)。
Severity
中
Patch Name
Cisco IP Phone 8800 Series设备拒绝服务漏洞的补丁
Patch Description
Cisco IP Phone 8800 Series devices是美国思科(Cisco)公司的一款提供视频和VoIP通信功能的IP电话。Session Initiation Protocol(SIP)是使用在其中的一个会话启动协议。 Cisco IP Phone 8800 Series设备中的Session Initiation Protocol (SIP)调用的处理存在拒绝服务漏洞,该漏洞源于程序未能对SIP数据包包头执行充分的输入验证。远程攻击者可通过向目标电话发送畸形的SIP数据包利用该漏洞造成拒绝服务(SIP进程重启)。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171129-ipp

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171129-ipp
Impacted products
Name
Cisco IP Phone 8800 Series 11.0(0.1)
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "102003"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-12328"
    }
  },
  "description": "Cisco IP Phone 8800 Series devices\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u4e00\u6b3e\u63d0\u4f9b\u89c6\u9891\u548cVoIP\u901a\u4fe1\u529f\u80fd\u7684IP\u7535\u8bdd\u3002Session Initiation Protocol\uff08SIP\uff09\u662f\u4f7f\u7528\u5728\u5176\u4e2d\u7684\u4e00\u4e2a\u4f1a\u8bdd\u542f\u52a8\u534f\u8bae\u3002\r\n\r\nCisco IP Phone 8800 Series\u8bbe\u5907\u4e2d\u7684Session Initiation Protocol (SIP)\u8c03\u7528\u7684\u5904\u7406\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u5bf9SIP\u6570\u636e\u5305\u5305\u5934\u6267\u884c\u5145\u5206\u7684\u8f93\u5165\u9a8c\u8bc1\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5411\u76ee\u6807\u7535\u8bdd\u53d1\u9001\u7578\u5f62\u7684SIP\u6570\u636e\u5305\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08SIP\u8fdb\u7a0b\u91cd\u542f\uff09\u3002",
  "discovererName": "Cisco",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171129-ipp",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-36397",
  "openTime": "2017-12-06",
  "patchDescription": "Cisco IP Phone 8800 Series devices\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u4e00\u6b3e\u63d0\u4f9b\u89c6\u9891\u548cVoIP\u901a\u4fe1\u529f\u80fd\u7684IP\u7535\u8bdd\u3002Session Initiation Protocol\uff08SIP\uff09\u662f\u4f7f\u7528\u5728\u5176\u4e2d\u7684\u4e00\u4e2a\u4f1a\u8bdd\u542f\u52a8\u534f\u8bae\u3002\r\n\r\nCisco IP Phone 8800 Series\u8bbe\u5907\u4e2d\u7684Session Initiation Protocol (SIP)\u8c03\u7528\u7684\u5904\u7406\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u5bf9SIP\u6570\u636e\u5305\u5305\u5934\u6267\u884c\u5145\u5206\u7684\u8f93\u5165\u9a8c\u8bc1\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5411\u76ee\u6807\u7535\u8bdd\u53d1\u9001\u7578\u5f62\u7684SIP\u6570\u636e\u5305\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u62d2\u7edd\u670d\u52a1\uff08SIP\u8fdb\u7a0b\u91cd\u542f\uff09\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": "Cisco IP Phone 8800 Series\u8bbe\u5907\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Cisco IP Phone 8800 Series 11.0(0.1)"
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20171129-ipp",
  "serverity": "\u4e2d",
  "submitTime": "2017-12-04",
  "title": "Cisco IP Phone 8800 Series\u8bbe\u5907\u62d2\u7edd\u670d\u52a1\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.