CNVD-2016-12844

Vulnerability from cnvd - Published: 2016-12-22
VLAI
Title
Huawei CloudEngine 12800交换机内存泄露漏洞(CNVD-2016-12844)
Description
Huawei CloudEngine 12800是中国华为(Huawei)公司的交换机设备。 Huawei CloudEngine 12800交换机内存泄露漏洞。由于LDP处理模块处理报文发现某些字段值异常时,未对申请处理报文的内存进行释放,导致内存泄露。未经身份认证的攻击者利用漏洞向受影响设备发送特殊的LDP(Label Distribution Protocol)报文可导致内存泄漏。
Severity
低
Patch Name
Huawei CloudEngine 12800交换机内存泄露漏洞(CNVD-2016-12844)的补丁
Patch Description
Huawei CloudEngine 12800是中国华为(Huawei)公司的交换机设备。 Huawei CloudEngine 12800交换机内存泄露漏洞。由于LDP处理模块处理报文发现某些字段值异常时,未对申请处理报文的内存进行释放,导致内存泄露。未经身份认证的攻击者利用漏洞向受影响设备发送特殊的LDP(Label Distribution Protocol)报文可导致内存泄漏。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

华为已发布版本修复该漏洞,参考如下链接: http://www.huawei.com/cn/psirt/security-advisories/2016/huawei-sa-20161221-01-ldp-cn

Reference
http://www.huawei.com/cn/psirt/security-advisories/2016/huawei-sa-20161221-01-ldp-cn
Impacted products
Name
['Huawei CloudEngine 12800 V100R003C00', 'Huawei CloudEngine 12800 V100R003C10', 'Huawei CloudEngine 12800 V100R005C00', 'Huawei CloudEngine 12800 V100R005C10', 'Huawei CloudEngine 12800 V100R006C00']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-8784"
    }
  },
  "description": "Huawei CloudEngine 12800\u662f\u4e2d\u56fd\u534e\u4e3a\uff08Huawei\uff09\u516c\u53f8\u7684\u4ea4\u6362\u673a\u8bbe\u5907\u3002\r\n\r\nHuawei CloudEngine 12800\u4ea4\u6362\u673a\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e\u3002\u7531\u4e8eLDP\u5904\u7406\u6a21\u5757\u5904\u7406\u62a5\u6587\u53d1\u73b0\u67d0\u4e9b\u5b57\u6bb5\u503c\u5f02\u5e38\u65f6\uff0c\u672a\u5bf9\u7533\u8bf7\u5904\u7406\u62a5\u6587\u7684\u5185\u5b58\u8fdb\u884c\u91ca\u653e\uff0c\u5bfc\u81f4\u5185\u5b58\u6cc4\u9732\u3002\u672a\u7ecf\u8eab\u4efd\u8ba4\u8bc1\u7684\u653b\u51fb\u8005\u5229\u7528\u6f0f\u6d1e\u5411\u53d7\u5f71\u54cd\u8bbe\u5907\u53d1\u9001\u7279\u6b8a\u7684LDP\uff08Label Distribution Protocol\uff09\u62a5\u6587\u53ef\u5bfc\u81f4\u5185\u5b58\u6cc4\u6f0f\u3002",
  "discovererName": "Huawei",
  "formalWay": "\u534e\u4e3a\u5df2\u53d1\u5e03\u7248\u672c\u4fee\u590d\u8be5\u6f0f\u6d1e\uff0c\u53c2\u8003\u5982\u4e0b\u94fe\u63a5\uff1a\r\nhttp://www.huawei.com/cn/psirt/security-advisories/2016/huawei-sa-20161221-01-ldp-cn",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2016-12844",
  "openTime": "2016-12-22",
  "patchDescription": "Huawei CloudEngine 12800\u662f\u4e2d\u56fd\u534e\u4e3a\uff08Huawei\uff09\u516c\u53f8\u7684\u4ea4\u6362\u673a\u8bbe\u5907\u3002\r\n\r\nHuawei CloudEngine 12800\u4ea4\u6362\u673a\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e\u3002\u7531\u4e8eLDP\u5904\u7406\u6a21\u5757\u5904\u7406\u62a5\u6587\u53d1\u73b0\u67d0\u4e9b\u5b57\u6bb5\u503c\u5f02\u5e38\u65f6\uff0c\u672a\u5bf9\u7533\u8bf7\u5904\u7406\u62a5\u6587\u7684\u5185\u5b58\u8fdb\u884c\u91ca\u653e\uff0c\u5bfc\u81f4\u5185\u5b58\u6cc4\u9732\u3002\u672a\u7ecf\u8eab\u4efd\u8ba4\u8bc1\u7684\u653b\u51fb\u8005\u5229\u7528\u6f0f\u6d1e\u5411\u53d7\u5f71\u54cd\u8bbe\u5907\u53d1\u9001\u7279\u6b8a\u7684LDP\uff08Label Distribution Protocol\uff09\u62a5\u6587\u53ef\u5bfc\u81f4\u5185\u5b58\u6cc4\u6f0f\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": "Huawei CloudEngine 12800\u4ea4\u6362\u673a\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2016-12844\uff09\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Huawei CloudEngine 12800 V100R003C00",
      "Huawei CloudEngine 12800 V100R003C10",
      "Huawei CloudEngine 12800 V100R005C00",
      "Huawei CloudEngine 12800 V100R005C10",
      "Huawei CloudEngine 12800 V100R006C00"
    ]
  },
  "referenceLink": "http://www.huawei.com/cn/psirt/security-advisories/2016/huawei-sa-20161221-01-ldp-cn",
  "serverity": "\u4f4e",
  "submitTime": "2016-12-22",
  "title": "Huawei CloudEngine 12800\u4ea4\u6362\u673a\u5185\u5b58\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2016-12844\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.