CNVD-2018-23266

Vulnerability from cnvd - Published: 2018-11-16
VLAI
Title
IOBit Malware Fighter栈缓冲区溢出漏洞(CNVD-2018-23266)
Description
IObit Malware Fighter是一款适用于Microsoft Windows操作系统的反恶意软件和防病毒程序,旨在删除和防范恶意软件,包括特洛伊木马、rootkit及勒索软件。 IOBit Malware Fighter 6.2中的RegFilter.sys存在栈的缓冲区溢出漏洞。攻击者可使用大小超过8个字节的IOCTL 0x8006E040利用该漏洞导致拒绝服务或能以root权限执行代码。
Severity
高
Formal description

厂商尚未提供漏洞修复方案,请关注厂商主页更新: https://www.iobit.com/en/malware-fighter.php

Reference
https://downwithup.github.io/CVEPosts.html
Impacted products
Name
IObit Malware Fighter 6.2
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-19086"
    }
  },
  "description": "IObit Malware Fighter\u662f\u4e00\u6b3e\u9002\u7528\u4e8eMicrosoft Windows\u64cd\u4f5c\u7cfb\u7edf\u7684\u53cd\u6076\u610f\u8f6f\u4ef6\u548c\u9632\u75c5\u6bd2\u7a0b\u5e8f\uff0c\u65e8\u5728\u5220\u9664\u548c\u9632\u8303\u6076\u610f\u8f6f\u4ef6\uff0c\u5305\u62ec\u7279\u6d1b\u4f0a\u6728\u9a6c\u3001rootkit\u53ca\u52d2\u7d22\u8f6f\u4ef6\u3002\n\nIOBit Malware Fighter 6.2\u4e2d\u7684RegFilter.sys\u5b58\u5728\u6808\u7684\u7f13\u51b2\u533a\u6ea2\u51fa\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u4f7f\u7528\u5927\u5c0f\u8d85\u8fc78\u4e2a\u5b57\u8282\u7684IOCTL 0x8006E040\u5229\u7528\u8be5\u6f0f\u6d1e\u5bfc\u81f4\u62d2\u7edd\u670d\u52a1\u6216\u80fd\u4ee5root\u6743\u9650\u6267\u884c\u4ee3\u7801\u3002",
  "discovererName": "unknown",
  "formalWay": "\u5382\u5546\u5c1a\u672a\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u590d\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u66f4\u65b0\uff1a\r\nhttps://www.iobit.com/en/malware-fighter.php",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-23266",
  "openTime": "2018-11-16",
  "products": {
    "product": "IObit Malware Fighter 6.2"
  },
  "referenceLink": "https://downwithup.github.io/CVEPosts.html",
  "serverity": "\u9ad8",
  "submitTime": "2018-11-12",
  "title": "IOBit Malware Fighter\u6808\u7f13\u51b2\u533a\u6ea2\u51fa\u6f0f\u6d1e\uff08CNVD-2018-23266\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.