CNVD-2020-03900

Vulnerability from cnvd - Published: 2020-02-14
VLAI
Title
DLINKDIR-859系列路由器存在命令执行漏洞
Description
D-Link DIR-859是中国台湾友讯(D-Link)公司的一款无线路由器。 DLINK旗下DIR-859系列路由器存在远程命令执行漏洞,攻击者可以利用该漏洞以root权限在⽬标设备上执行任意命令。
Severity
高
Patch Name
DLINKDIR-859路由器v1.06B01 BETA01存在命令执行漏洞
Patch Description
已由CNVD通过软件生产厂商公开联系渠道向其邮件通报,由其后续提供解决方案并协调相关用户单位处置。
Formal description

厂商已修复该漏洞,请关注厂商主页更新: https://www.dlink.com

Impacted products
Name
DLink DIR-859 v1.06B01 BETA01
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-17621"
    }
  },
  "description": "D-Link DIR-859\u662f\u4e2d\u56fd\u53f0\u6e7e\u53cb\u8baf(D-Link)\u516c\u53f8\u7684\u4e00\u6b3e\u65e0\u7ebf\u8def\u7531\u5668\u3002\n\nDLINK\u65d7\u4e0bDIR-859\u7cfb\u5217\u8def\u7531\u5668\u5b58\u5728\u8fdc\u7a0b\u547d\u4ee4\u6267\u884c\u6f0f\u6d1e\uff0c\u653b\u51fb\u8005\u53ef\u4ee5\u5229\u7528\u8be5\u6f0f\u6d1e\u4ee5root\u6743\u9650\u5728\u2f6c\u6807\u8bbe\u5907\u4e0a\u6267\u884c\u4efb\u610f\u547d\u4ee4\u3002",
  "discovererName": "\u9752\u6d77\u5206\u4e2d\u5fc3",
  "formalWay": "\u5382\u5546\u5df2\u4fee\u590d\u8be5\u6f0f\u6d1e\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttps://www.dlink.com",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-03900",
  "openTime": "2020-02-14",
  "patchDescription": "\u5df2\u7531CNVD\u901a\u8fc7\u8f6f\u4ef6\u751f\u4ea7\u5382\u5546\u516c\u5f00\u8054\u7cfb\u6e20\u9053\u5411\u5176\u90ae\u4ef6\u901a\u62a5\uff0c\u7531\u5176\u540e\u7eed\u63d0\u4f9b\u89e3\u51b3\u65b9\u6848\u5e76\u534f\u8c03\u76f8\u5173\u7528\u6237\u5355\u4f4d\u5904\u7f6e\u3002",
  "patchName": "DLINKDIR-859\u8def\u7531\u5668v1.06B01 BETA01\u5b58\u5728\u547d\u4ee4\u6267\u884c\u6f0f\u6d1e",
  "products": {
    "product": "DLink DIR-859 v1.06B01 BETA01"
  },
  "serverity": "\u9ad8",
  "submitTime": "2019-12-31",
  "title": "DLINKDIR-859\u7cfb\u5217\u8def\u7531\u5668\u5b58\u5728\u547d\u4ee4\u6267\u884c\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.