CNVD-2018-14579

Vulnerability from cnvd - Published: 2018-08-03
VLAI
Title
Cisco Nexus 3000和9000 Series Switches NX-OS拒绝服务漏洞
Description
Cisco Nexus 3000和9000 Series Switches都是美国思科(Cisco)公司的不同系列的交换机设备。NX-OS是运行在其中的一套交换机使用的数据中心级操作系统软件。 Cisco Nexus 3000和9000 Series Switches中的NX-OS(在standalone NX-OS模式下)的CLI命令及相关联的Simple Network Management Protocol (SNMP) MIB的实现存在拒绝服务漏洞,该漏洞源于程序未能正确的实现CLI命令。远程攻击者可通过对受影响的设备进行身份验证并重复的发布CLI命令或SNMP轮询请求利用该漏洞造成系统内存耗尽。
Severity
高
Patch Name
Cisco Nexus 3000和9000 Series Switches NX-OS拒绝服务漏洞的补丁
Patch Description
Cisco Nexus 3000和9000 Series Switches都是美国思科(Cisco)公司的不同系列的交换机设备。NX-OS是运行在其中的一套交换机使用的数据中心级操作系统软件。 Cisco Nexus 3000和9000 Series Switches中的NX-OS(在standalone NX-OS模式下)的CLI命令及相关联的Simple Network Management Protocol (SNMP) MIB的实现存在拒绝服务漏洞,该漏洞源于程序未能正确的实现CLI命令。远程攻击者可通过对受影响的设备进行身份验证并重复的发布CLI命令或SNMP轮询请求利用该漏洞造成系统内存耗尽。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

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

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180620-n3k-n9k-clisnmp
Impacted products
Name
['Cisco Nexus 3000 Series Switche', 'Cisco Nexus 9000 Series Switches']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-0309",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0309"
    }
  },
  "description": "Cisco Nexus 3000\u548c9000 Series Switches\u90fd\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u4e0d\u540c\u7cfb\u5217\u7684\u4ea4\u6362\u673a\u8bbe\u5907\u3002NX-OS\u662f\u8fd0\u884c\u5728\u5176\u4e2d\u7684\u4e00\u5957\u4ea4\u6362\u673a\u4f7f\u7528\u7684\u6570\u636e\u4e2d\u5fc3\u7ea7\u64cd\u4f5c\u7cfb\u7edf\u8f6f\u4ef6\u3002\r\n\r\nCisco Nexus 3000\u548c9000 Series Switches\u4e2d\u7684NX-OS(\u5728standalone NX-OS\u6a21\u5f0f\u4e0b)\u7684CLI\u547d\u4ee4\u53ca\u76f8\u5173\u8054\u7684Simple Network Management Protocol (SNMP) MIB\u7684\u5b9e\u73b0\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u7684\u5b9e\u73b0CLI\u547d\u4ee4\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5bf9\u53d7\u5f71\u54cd\u7684\u8bbe\u5907\u8fdb\u884c\u8eab\u4efd\u9a8c\u8bc1\u5e76\u91cd\u590d\u7684\u53d1\u5e03CLI\u547d\u4ee4\u6216SNMP\u8f6e\u8be2\u8bf7\u6c42\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u7cfb\u7edf\u5185\u5b58\u8017\u5c3d\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-20180620-n3k-n9k-clisnmp",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-14579",
  "openTime": "2018-08-03",
  "patchDescription": "Cisco Nexus 3000\u548c9000 Series Switches\u90fd\u662f\u7f8e\u56fd\u601d\u79d1\uff08Cisco\uff09\u516c\u53f8\u7684\u4e0d\u540c\u7cfb\u5217\u7684\u4ea4\u6362\u673a\u8bbe\u5907\u3002NX-OS\u662f\u8fd0\u884c\u5728\u5176\u4e2d\u7684\u4e00\u5957\u4ea4\u6362\u673a\u4f7f\u7528\u7684\u6570\u636e\u4e2d\u5fc3\u7ea7\u64cd\u4f5c\u7cfb\u7edf\u8f6f\u4ef6\u3002\r\n\r\nCisco Nexus 3000\u548c9000 Series Switches\u4e2d\u7684NX-OS(\u5728standalone NX-OS\u6a21\u5f0f\u4e0b)\u7684CLI\u547d\u4ee4\u53ca\u76f8\u5173\u8054\u7684Simple Network Management Protocol (SNMP) MIB\u7684\u5b9e\u73b0\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u672a\u80fd\u6b63\u786e\u7684\u5b9e\u73b0CLI\u547d\u4ee4\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u5bf9\u53d7\u5f71\u54cd\u7684\u8bbe\u5907\u8fdb\u884c\u8eab\u4efd\u9a8c\u8bc1\u5e76\u91cd\u590d\u7684\u53d1\u5e03CLI\u547d\u4ee4\u6216SNMP\u8f6e\u8be2\u8bf7\u6c42\u5229\u7528\u8be5\u6f0f\u6d1e\u9020\u6210\u7cfb\u7edf\u5185\u5b58\u8017\u5c3d\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 Nexus 3000\u548c9000 Series Switches NX-OS\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Cisco Nexus 3000 Series Switche",
      "Cisco Nexus 9000 Series Switches"
    ]
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20180620-n3k-n9k-clisnmp",
  "serverity": "\u9ad8",
  "submitTime": "2018-06-26",
  "title": "Cisco Nexus 3000\u548c9000 Series Switches NX-OS\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.