CNVD-2017-05550

Vulnerability from cnvd - Published: 2017-04-28
VLAI
Title
Zabbix存在远程代码执行和数据库写入漏洞
Description
zabbix是一个基于WEB界面的提供分布式系统监视以及网络监视功能的企业级的开源解决方案。 Zabbix 2.4.x版本的trapper command功能存在远程代码执行漏洞,特定的数据包可造成命令注入,进而远程执行代码,攻击者可以从一个Zabbix proxy发起请求从而促发漏洞。 Zabbix 2.4.x版本的trapper功能存在数据库写入漏洞,特定的恶意trapper数据包可通过database的逻辑检查,造成数据库写入,攻击者可通过中间人的方式修改zabbix proxy和Server间的请求来触发漏洞。
Severity
高
Formal description

厂商尚未提供漏洞修补方案,请关注厂商主页及时更新: http://www.zabbix.com http://blog.talosintelligence.com/2017/04/zabbix-multiple-vulns.html

Reference
http://blog.talosintelligence.com/2017/04/zabbix-multiple-vulns.html http://www.talosintelligence.com/reports/TALOS-2017-0325/ http://www.talosintelligence.com/reports/TALOS-2017-0326/
Impacted products
Name
Zabbix Zabbix >=2.4.7,<=2.4.8r1
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-2824"
    }
  },
  "description": "zabbix\u662f\u4e00\u4e2a\u57fa\u4e8eWEB\u754c\u9762\u7684\u63d0\u4f9b\u5206\u5e03\u5f0f\u7cfb\u7edf\u76d1\u89c6\u4ee5\u53ca\u7f51\u7edc\u76d1\u89c6\u529f\u80fd\u7684\u4f01\u4e1a\u7ea7\u7684\u5f00\u6e90\u89e3\u51b3\u65b9\u6848\u3002\r\n\r\nZabbix 2.4.x\u7248\u672c\u7684trapper command\u529f\u80fd\u5b58\u5728\u8fdc\u7a0b\u4ee3\u7801\u6267\u884c\u6f0f\u6d1e\uff0c\u7279\u5b9a\u7684\u6570\u636e\u5305\u53ef\u9020\u6210\u547d\u4ee4\u6ce8\u5165\uff0c\u8fdb\u800c\u8fdc\u7a0b\u6267\u884c\u4ee3\u7801\uff0c\u653b\u51fb\u8005\u53ef\u4ee5\u4ece\u4e00\u4e2aZabbix proxy\u53d1\u8d77\u8bf7\u6c42\u4ece\u800c\u4fc3\u53d1\u6f0f\u6d1e\u3002\r\nZabbix 2.4.x\u7248\u672c\u7684trapper\u529f\u80fd\u5b58\u5728\u6570\u636e\u5e93\u5199\u5165\u6f0f\u6d1e\uff0c\u7279\u5b9a\u7684\u6076\u610ftrapper\u6570\u636e\u5305\u53ef\u901a\u8fc7database\u7684\u903b\u8f91\u68c0\u67e5\uff0c\u9020\u6210\u6570\u636e\u5e93\u5199\u5165\uff0c\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u4e2d\u95f4\u4eba\u7684\u65b9\u5f0f\u4fee\u6539zabbix  proxy\u548cServer\u95f4\u7684\u8bf7\u6c42\u6765\u89e6\u53d1\u6f0f\u6d1e\u3002",
  "discovererName": "Lilith Wyatt of Cisco ASIG",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u8865\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u53ca\u65f6\u66f4\u65b0\uff1a \r\nhttp://www.zabbix.com\r\nhttp://blog.talosintelligence.com/2017/04/zabbix-multiple-vulns.html",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-05550",
  "openTime": "2017-04-28",
  "products": {
    "product": "Zabbix Zabbix  \u003e=2.4.7\uff0c\u003c=2.4.8r1"
  },
  "referenceLink": "http://blog.talosintelligence.com/2017/04/zabbix-multiple-vulns.html\r\nhttp://www.talosintelligence.com/reports/TALOS-2017-0325/\r\nhttp://www.talosintelligence.com/reports/TALOS-2017-0326/",
  "serverity": "\u9ad8",
  "submitTime": "2017-04-28",
  "title": "Zabbix\u5b58\u5728\u8fdc\u7a0b\u4ee3\u7801\u6267\u884c\u548c\u6570\u636e\u5e93\u5199\u5165\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.