CNVD-2018-19617

Vulnerability from cnvd - Published: 2018-09-21
VLAI
Title
IBM GPFS拒绝服务漏洞
Description
IBM GPFS是美国IBM公司的一套专为PB级存储管理而优化的企业文件管理系统。IBM Spectrum Scale是一套基于IBM GPFS的可扩展的数据及文件管理解决方案。该方案支持帮助客户减少存储成本,同时提高云、大数据和分析环境中的安全性和管理效率等。 IBM GPFS中存在拒绝服务漏洞,本地攻击者可通过访问存储在GPFS文件系统上的文件或执行一个存储在GPFS文件系统上的特制文件,利用该漏洞在运行GPFS的节点上造成内核错误。
Severity
中
Patch Name
IBM GPFS拒绝服务漏洞的补丁
Patch Description
IBM GPFS是美国IBM公司的一套专为PB级存储管理而优化的企业文件管理系统。IBM Spectrum Scale是一套基于IBM GPFS的可扩展的数据及文件管理解决方案。该方案支持帮助客户减少存储成本,同时提高云、大数据和分析环境中的安全性和管理效率等。 IBM GPFS中存在拒绝服务漏洞,本地攻击者可通过访问存储在GPFS文件系统上的文件或执行一个存储在GPFS文件系统上的特制文件,利用该漏洞在运行GPFS的节点上造成内核错误。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://www.ibm.com/support/docview.wss?uid=ibm10730967

Reference
https://exchange.xforce.ibmcloud.com/vulnerabilities/148805 https://www.ibm.com/support/docview.wss?uid=ibm10730967
Impacted products
Name
['IBM Spectrum Scale 5.0.1.0', 'IBM Spectrum Scale 5.0.1.1']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-1782"
    }
  },
  "description": "IBM GPFS\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u4e13\u4e3aPB\u7ea7\u5b58\u50a8\u7ba1\u7406\u800c\u4f18\u5316\u7684\u4f01\u4e1a\u6587\u4ef6\u7ba1\u7406\u7cfb\u7edf\u3002IBM Spectrum Scale\u662f\u4e00\u5957\u57fa\u4e8eIBM GPFS\u7684\u53ef\u6269\u5c55\u7684\u6570\u636e\u53ca\u6587\u4ef6\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002\u8be5\u65b9\u6848\u652f\u6301\u5e2e\u52a9\u5ba2\u6237\u51cf\u5c11\u5b58\u50a8\u6210\u672c\uff0c\u540c\u65f6\u63d0\u9ad8\u4e91\u3001\u5927\u6570\u636e\u548c\u5206\u6790\u73af\u5883\u4e2d\u7684\u5b89\u5168\u6027\u548c\u7ba1\u7406\u6548\u7387\u7b49\u3002\r\n\r\nIBM GPFS\u4e2d\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u672c\u5730\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u8bbf\u95ee\u5b58\u50a8\u5728GPFS\u6587\u4ef6\u7cfb\u7edf\u4e0a\u7684\u6587\u4ef6\u6216\u6267\u884c\u4e00\u4e2a\u5b58\u50a8\u5728GPFS\u6587\u4ef6\u7cfb\u7edf\u4e0a\u7684\u7279\u5236\u6587\u4ef6\uff0c\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u8fd0\u884cGPFS\u7684\u8282\u70b9\u4e0a\u9020\u6210\u5185\u6838\u9519\u8bef\u3002",
  "discovererName": "Ryan Adamson",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://www.ibm.com/support/docview.wss?uid=ibm10730967",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-19617",
  "openTime": "2018-09-21",
  "patchDescription": "IBM GPFS\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u4e13\u4e3aPB\u7ea7\u5b58\u50a8\u7ba1\u7406\u800c\u4f18\u5316\u7684\u4f01\u4e1a\u6587\u4ef6\u7ba1\u7406\u7cfb\u7edf\u3002IBM Spectrum Scale\u662f\u4e00\u5957\u57fa\u4e8eIBM GPFS\u7684\u53ef\u6269\u5c55\u7684\u6570\u636e\u53ca\u6587\u4ef6\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002\u8be5\u65b9\u6848\u652f\u6301\u5e2e\u52a9\u5ba2\u6237\u51cf\u5c11\u5b58\u50a8\u6210\u672c\uff0c\u540c\u65f6\u63d0\u9ad8\u4e91\u3001\u5927\u6570\u636e\u548c\u5206\u6790\u73af\u5883\u4e2d\u7684\u5b89\u5168\u6027\u548c\u7ba1\u7406\u6548\u7387\u7b49\u3002\r\n\r\nIBM GPFS\u4e2d\u5b58\u5728\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\uff0c\u672c\u5730\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u8bbf\u95ee\u5b58\u50a8\u5728GPFS\u6587\u4ef6\u7cfb\u7edf\u4e0a\u7684\u6587\u4ef6\u6216\u6267\u884c\u4e00\u4e2a\u5b58\u50a8\u5728GPFS\u6587\u4ef6\u7cfb\u7edf\u4e0a\u7684\u7279\u5236\u6587\u4ef6\uff0c\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u8fd0\u884cGPFS\u7684\u8282\u70b9\u4e0a\u9020\u6210\u5185\u6838\u9519\u8bef\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": "IBM GPFS\u62d2\u7edd\u670d\u52a1\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "IBM Spectrum Scale 5.0.1.0",
      "IBM Spectrum Scale 5.0.1.1"
    ]
  },
  "referenceLink": "https://exchange.xforce.ibmcloud.com/vulnerabilities/148805\r\nhttps://www.ibm.com/support/docview.wss?uid=ibm10730967",
  "serverity": "\u4e2d",
  "submitTime": "2018-09-21",
  "title": "IBM GPFS\u62d2\u7edd\u670d\u52a1\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.