CNVD-2015-07794

Vulnerability from cnvd - Published: 2015-11-26
VLAI
Title
Huawei AR路由器SFTP服务器目录遍历漏洞
Description
Huawei AR系列路由器是基于华为专有VRP的下一代企业级路由器,集成了路由、交换、3G、WLAN、语音和安全功能。 Huawei AR 120, 150, 160, 200, 500, 1200, 2200, 3200, 3600路由器(V200R006SPH003之前版本),用作SFTP服务器时未严格检查用户访问的目录,存在目录遍历漏洞,经验证的远程用户利用此漏洞可访问任意目录,导致信息泄露。
Severity
中
Patch Name
Huawei AR路由器SFTP服务器目录遍历漏洞的补丁
Patch Description
Huawei AR系列路由器是基于华为专有VRP的下一代企业级路由器,集成了路由、交换、3G、WLAN、语音和安全功能。 Huawei AR 120, 150, 160, 200, 500, 1200, 2200, 3200, 3600路由器(V200R006SPH003之前版本),用作SFTP服务器时未严格检查用户访问的目录,存在目录遍历漏洞,经验证的远程用户利用此漏洞可访问任意目录,导致信息泄露。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已经发布了升级补丁以修复这个安全问题,请到厂商的主页下载: http://www1.huawei.com/en/security/psirt/security-bulletins/security-advisories/hw-461676.htm http://www.huawei.com/en/security/psirt/report-vulnerabilities/index.htm

Reference
http://www.huawei.com/en/security/psirt/report-vulnerabilities/index.htm
Impacted products
Name
['Huawei AR 150', 'Huawei AR 200', 'Huawei AR 1200', 'Huawei AR 2200', 'Huawei AR 3200', 'Huawei AR 120', 'Huawei AR 160', 'Huawei AR 500', 'Huawei AR 3600']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-8228"
    }
  },
  "description": "Huawei AR\u7cfb\u5217\u8def\u7531\u5668\u662f\u57fa\u4e8e\u534e\u4e3a\u4e13\u6709VRP\u7684\u4e0b\u4e00\u4ee3\u4f01\u4e1a\u7ea7\u8def\u7531\u5668\uff0c\u96c6\u6210\u4e86\u8def\u7531\u3001\u4ea4\u6362\u30013G\u3001WLAN\u3001\u8bed\u97f3\u548c\u5b89\u5168\u529f\u80fd\u3002\r\n\r\nHuawei AR 120, 150, 160, 200, 500, 1200, 2200, 3200, 3600\u8def\u7531\u5668\uff08V200R006SPH003\u4e4b\u524d\u7248\u672c\uff09\uff0c\u7528\u4f5cSFTP\u670d\u52a1\u5668\u65f6\u672a\u4e25\u683c\u68c0\u67e5\u7528\u6237\u8bbf\u95ee\u7684\u76ee\u5f55\uff0c\u5b58\u5728\u76ee\u5f55\u904d\u5386\u6f0f\u6d1e\uff0c\u7ecf\u9a8c\u8bc1\u7684\u8fdc\u7a0b\u7528\u6237\u5229\u7528\u6b64\u6f0f\u6d1e\u53ef\u8bbf\u95ee\u4efb\u610f\u76ee\u5f55\uff0c\u5bfc\u81f4\u4fe1\u606f\u6cc4\u9732\u3002",
  "discovererName": "Huawei",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u7ecf\u53d1\u5e03\u4e86\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u8fd9\u4e2a\u5b89\u5168\u95ee\u9898\uff0c\u8bf7\u5230\u5382\u5546\u7684\u4e3b\u9875\u4e0b\u8f7d\uff1a\r\nhttp://www1.huawei.com/en/security/psirt/security-bulletins/security-advisories/hw-461676.htm\r\nhttp://www.huawei.com/en/security/psirt/report-vulnerabilities/index.htm",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2015-07794",
  "openTime": "2015-11-26",
  "patchDescription": "Huawei AR\u7cfb\u5217\u8def\u7531\u5668\u662f\u57fa\u4e8e\u534e\u4e3a\u4e13\u6709VRP\u7684\u4e0b\u4e00\u4ee3\u4f01\u4e1a\u7ea7\u8def\u7531\u5668\uff0c\u96c6\u6210\u4e86\u8def\u7531\u3001\u4ea4\u6362\u30013G\u3001WLAN\u3001\u8bed\u97f3\u548c\u5b89\u5168\u529f\u80fd\u3002\r\n\r\nHuawei AR 120, 150, 160, 200, 500, 1200, 2200, 3200, 3600\u8def\u7531\u5668\uff08V200R006SPH003\u4e4b\u524d\u7248\u672c\uff09\uff0c\u7528\u4f5cSFTP\u670d\u52a1\u5668\u65f6\u672a\u4e25\u683c\u68c0\u67e5\u7528\u6237\u8bbf\u95ee\u7684\u76ee\u5f55\uff0c\u5b58\u5728\u76ee\u5f55\u904d\u5386\u6f0f\u6d1e\uff0c\u7ecf\u9a8c\u8bc1\u7684\u8fdc\u7a0b\u7528\u6237\u5229\u7528\u6b64\u6f0f\u6d1e\u53ef\u8bbf\u95ee\u4efb\u610f\u76ee\u5f55\uff0c\u5bfc\u81f4\u4fe1\u606f\u6cc4\u9732\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 AR\u8def\u7531\u5668SFTP\u670d\u52a1\u5668\u76ee\u5f55\u904d\u5386\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Huawei AR 150",
      "Huawei AR 200",
      "Huawei AR 1200",
      "Huawei AR 2200",
      "Huawei AR 3200",
      "Huawei AR 120",
      "Huawei AR  160",
      "Huawei AR  500",
      "Huawei AR  3600"
    ]
  },
  "referenceLink": "http://www.huawei.com/en/security/psirt/report-vulnerabilities/index.htm",
  "serverity": "\u4e2d",
  "submitTime": "2015-11-25",
  "title": "Huawei AR\u8def\u7531\u5668SFTP\u670d\u52a1\u5668\u76ee\u5f55\u904d\u5386\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.