CNVD-2016-02720

Vulnerability from cnvd - Published: 2016-05-05
VLAI
Title
华为多款交换机存在输入校验漏洞
Description
S5700系列交换机是华为公司为满足大带宽接入和以太网多业务汇聚而推出的的全千兆以太网交换机。S12700系列交换机是面向下一代园区网核心而专门设计开发的敏捷交换机。 华为多款交换机存在输入校验漏洞。由于设备缺少对报文的有效校验,当设备的Debug开关打开时,攻击者可以构造畸形DNS报文发向设备,造成设备拒绝服务及远程代码执行。
Severity
中
Patch Name
华为多款交换机存在输入校验漏洞的补丁
Patch Description
S5700系列交换机是华为公司为满足大带宽接入和以太网多业务汇聚而推出的的全千兆以太网交换机。S12700系列交换机是面向下一代园区网核心而专门设计开发的敏捷交换机。 华为多款交换机存在输入校验漏洞。由于设备缺少对报文的有效校验,当设备的Debug开关打开时,攻击者可以构造畸形DNS报文发向设备,造成设备拒绝服务及远程代码执行。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布安全公告修复该漏洞,请及时关注厂商主页更新: http://www.huawei.com/cn/psirt/security-advisories/huawei-sa-20160427-01-dns-cn

Reference
http://www.huawei.com/cn/psirt/security-advisories/huawei-sa-20160427-01-dns-cn
Impacted products
Name
['Huawei S12700 V200R005C00SPC300', 'Huawei S5700 V200R001C00', 'Huawei S5700 V200R002C00SPC100', 'Huawei S5700 V200R003C00SPC300', 'Huawei S5700 V200R005C00']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-4087"
    }
  },
  "description": "S5700\u7cfb\u5217\u4ea4\u6362\u673a\u662f\u534e\u4e3a\u516c\u53f8\u4e3a\u6ee1\u8db3\u5927\u5e26\u5bbd\u63a5\u5165\u548c\u4ee5\u592a\u7f51\u591a\u4e1a\u52a1\u6c47\u805a\u800c\u63a8\u51fa\u7684\u7684\u5168\u5343\u5146\u4ee5\u592a\u7f51\u4ea4\u6362\u673a\u3002S12700\u7cfb\u5217\u4ea4\u6362\u673a\u662f\u9762\u5411\u4e0b\u4e00\u4ee3\u56ed\u533a\u7f51\u6838\u5fc3\u800c\u4e13\u95e8\u8bbe\u8ba1\u5f00\u53d1\u7684\u654f\u6377\u4ea4\u6362\u673a\u3002\r\n\r\n\u534e\u4e3a\u591a\u6b3e\u4ea4\u6362\u673a\u5b58\u5728\u8f93\u5165\u6821\u9a8c\u6f0f\u6d1e\u3002\u7531\u4e8e\u8bbe\u5907\u7f3a\u5c11\u5bf9\u62a5\u6587\u7684\u6709\u6548\u6821\u9a8c\uff0c\u5f53\u8bbe\u5907\u7684Debug\u5f00\u5173\u6253\u5f00\u65f6\uff0c\u653b\u51fb\u8005\u53ef\u4ee5\u6784\u9020\u7578\u5f62DNS\u62a5\u6587\u53d1\u5411\u8bbe\u5907\uff0c\u9020\u6210\u8bbe\u5907\u62d2\u7edd\u670d\u52a1\u53ca\u8fdc\u7a0b\u4ee3\u7801\u6267\u884c\u3002",
  "discovererName": "\u534e\u4e3a",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u5b89\u5168\u516c\u544a\u4fee\u590d\u8be5\u6f0f\u6d1e\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttp://www.huawei.com/cn/psirt/security-advisories/huawei-sa-20160427-01-dns-cn",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2016-02720",
  "openTime": "2016-05-05",
  "patchDescription": "S5700\u7cfb\u5217\u4ea4\u6362\u673a\u662f\u534e\u4e3a\u516c\u53f8\u4e3a\u6ee1\u8db3\u5927\u5e26\u5bbd\u63a5\u5165\u548c\u4ee5\u592a\u7f51\u591a\u4e1a\u52a1\u6c47\u805a\u800c\u63a8\u51fa\u7684\u7684\u5168\u5343\u5146\u4ee5\u592a\u7f51\u4ea4\u6362\u673a\u3002S12700\u7cfb\u5217\u4ea4\u6362\u673a\u662f\u9762\u5411\u4e0b\u4e00\u4ee3\u56ed\u533a\u7f51\u6838\u5fc3\u800c\u4e13\u95e8\u8bbe\u8ba1\u5f00\u53d1\u7684\u654f\u6377\u4ea4\u6362\u673a\u3002\r\n\r\n\u534e\u4e3a\u591a\u6b3e\u4ea4\u6362\u673a\u5b58\u5728\u8f93\u5165\u6821\u9a8c\u6f0f\u6d1e\u3002\u7531\u4e8e\u8bbe\u5907\u7f3a\u5c11\u5bf9\u62a5\u6587\u7684\u6709\u6548\u6821\u9a8c\uff0c\u5f53\u8bbe\u5907\u7684Debug\u5f00\u5173\u6253\u5f00\u65f6\uff0c\u653b\u51fb\u8005\u53ef\u4ee5\u6784\u9020\u7578\u5f62DNS\u62a5\u6587\u53d1\u5411\u8bbe\u5907\uff0c\u9020\u6210\u8bbe\u5907\u62d2\u7edd\u670d\u52a1\u53ca\u8fdc\u7a0b\u4ee3\u7801\u6267\u884c\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": "\u534e\u4e3a\u591a\u6b3e\u4ea4\u6362\u673a\u5b58\u5728\u8f93\u5165\u6821\u9a8c\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Huawei S12700 V200R005C00SPC300",
      "Huawei S5700 V200R001C00",
      "Huawei S5700 V200R002C00SPC100",
      "Huawei S5700 V200R003C00SPC300",
      "Huawei S5700 V200R005C00"
    ]
  },
  "referenceLink": "http://www.huawei.com/cn/psirt/security-advisories/huawei-sa-20160427-01-dns-cn",
  "serverity": "\u4e2d",
  "submitTime": "2016-04-27",
  "title": "\u534e\u4e3a\u591a\u6b3e\u4ea4\u6362\u673a\u5b58\u5728\u8f93\u5165\u6821\u9a8c\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.