CNVD-2017-14427

Vulnerability from cnvd - Published: 2017-07-14
VLAI
Title
多款WiMAX路由器存在身份验证绕过漏洞
Description
WiMAX(微波存取全球互通), 是一种以IEEE-802.16标准为基础的通讯技术,可作为替代有线的宽频服务的另一种选择。 使用libmtk(MediaTek SDK库)的定制httpd插件的几个WiMAX路由器存在身份验证绕过漏洞。允许未经身份验证的远程攻击者利用该漏洞更改设备上的管理员密码。
Severity
高
Formal description

目前没有详细解决方案提供: http://www.kb.cert.org/vuls/id/350135

Reference
http://www.securityfocus.com/bid/99078
Impacted products
Name
['Mada Soho Wireless Router 2.10.13', 'GreenPacket OX-350 0', 'GreenPacket OX350 0', 'Huawei BM2022 2.10.14', 'Huawei HES-309M 0', 'Huawei HES-319M 0', 'Huawei HES-319M2W 0', 'Huawei HES-339M 0', 'ZTE OX-330P 0', 'ZyXEL MAX218M 2.00(UXG.0)D0', 'ZyXEL MAX218M1W 2.00(UXE.3)D0', 'ZyXEL MAX218MW 2.00(UXD.2)D0', 'ZyXEL MAX308M 2.00(UUA.3)D0', 'ZyXEL MAX318M 0', 'ZyXEL MAX338M 0']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "99078"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-3216"
    }
  },
  "description": "WiMAX(\u5fae\u6ce2\u5b58\u53d6\u5168\u7403\u4e92\u901a), \u662f\u4e00\u79cd\u4ee5IEEE-802.16\u6807\u51c6\u4e3a\u57fa\u7840\u7684\u901a\u8baf\u6280\u672f,\u53ef\u4f5c\u4e3a\u66ff\u4ee3\u6709\u7ebf\u7684\u5bbd\u9891\u670d\u52a1\u7684\u53e6\u4e00\u79cd\u9009\u62e9\u3002\r\n\r\n\u4f7f\u7528libmtk\uff08MediaTek SDK\u5e93\uff09\u7684\u5b9a\u5236httpd\u63d2\u4ef6\u7684\u51e0\u4e2aWiMAX\u8def\u7531\u5668\u5b58\u5728\u8eab\u4efd\u9a8c\u8bc1\u7ed5\u8fc7\u6f0f\u6d1e\u3002\u5141\u8bb8\u672a\u7ecf\u8eab\u4efd\u9a8c\u8bc1\u7684\u8fdc\u7a0b\u653b\u51fb\u8005\u5229\u7528\u8be5\u6f0f\u6d1e\u66f4\u6539\u8bbe\u5907\u4e0a\u7684\u7ba1\u7406\u5458\u5bc6\u7801\u3002",
  "discovererName": "Stefan Viehb\u00c3\u00b6ck, SEC Consult Vulnerability Lab",
  "formalWay": "\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u89e3\u51b3\u65b9\u6848\u63d0\u4f9b\uff1a\r\nhttp://www.kb.cert.org/vuls/id/350135",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-14427",
  "openTime": "2017-07-14",
  "products": {
    "product": [
      "Mada Soho Wireless Router 2.10.13",
      "GreenPacket OX-350 0",
      "GreenPacket OX350 0",
      "Huawei BM2022 2.10.14",
      "Huawei HES-309M 0",
      "Huawei HES-319M 0",
      "Huawei HES-319M2W 0",
      "Huawei HES-339M 0",
      "ZTE OX-330P 0",
      "ZyXEL   MAX218M 2.00(UXG.0)D0",
      "ZyXEL   MAX218M1W 2.00(UXE.3)D0",
      "ZyXEL   MAX218MW 2.00(UXD.2)D0",
      "ZyXEL   MAX308M 2.00(UUA.3)D0",
      "ZyXEL   MAX318M 0",
      "ZyXEL   MAX338M 0"
    ]
  },
  "referenceLink": "http://www.securityfocus.com/bid/99078",
  "serverity": "\u9ad8",
  "submitTime": "2017-06-12",
  "title": "\u591a\u6b3eWiMAX\u8def\u7531\u5668\u5b58\u5728\u8eab\u4efd\u9a8c\u8bc1\u7ed5\u8fc7\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.