CNVD-2019-25501

Vulnerability from cnvd - Published: 2019-08-02
VLAI
Title
IBM Water Operations for Waternamics和IBM Intelligent Operations Center信息泄露漏洞(CNVD-2019-25501)
Description
IBM Intelligent Operations Center(IOC)和IBM Water Operations for Waternamics都是美国IBM公司的产品。IBM Intelligent Operations Center是一套城市运营解决方案。该产品具有数据可视化、实时协作等功能。IBM Water Operations for Waternamics是一套适用于水资源运营商的预测分析平台。该平台包括适用于水资源运营商的基础设施管理、资产管理和运营管理等功能。 IBM Intelligent Operations Center和IBM Water Operations for Waternamics中存在信息泄露漏洞,该漏洞源于在默认情况下程序未能要求用户使用强度较高的密码,攻击者可通过暴力破解攻击利用该漏洞获取用户密码。
Severity
中
Formal description

厂商尚未提供漏洞修复方案,请关注厂商主页更新: https://www.ibm.com/

Reference
https://www.ibm.com/support/docview.wss?uid=ibm10880213 https://exchange.xforce.ibmcloud.com/vulnerabilities/157012
Impacted products
Name
['IBM Intelligent Operations Center >=5.1.0,<=5.2.0', 'IBM Intelligent Operations Center for Emergency Management >=5.1.0,<=5.1.0.6', 'IBM Water Operations for Waternamics >=5.1.0,<=5.2.1.1']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-4067",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-4067"
    }
  },
  "description": "IBM Intelligent Operations Center\uff08IOC\uff09\u548cIBM Water Operations for Waternamics\u90fd\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4ea7\u54c1\u3002IBM Intelligent Operations Center\u662f\u4e00\u5957\u57ce\u5e02\u8fd0\u8425\u89e3\u51b3\u65b9\u6848\u3002\u8be5\u4ea7\u54c1\u5177\u6709\u6570\u636e\u53ef\u89c6\u5316\u3001\u5b9e\u65f6\u534f\u4f5c\u7b49\u529f\u80fd\u3002IBM Water Operations for Waternamics\u662f\u4e00\u5957\u9002\u7528\u4e8e\u6c34\u8d44\u6e90\u8fd0\u8425\u5546\u7684\u9884\u6d4b\u5206\u6790\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u5305\u62ec\u9002\u7528\u4e8e\u6c34\u8d44\u6e90\u8fd0\u8425\u5546\u7684\u57fa\u7840\u8bbe\u65bd\u7ba1\u7406\u3001\u8d44\u4ea7\u7ba1\u7406\u548c\u8fd0\u8425\u7ba1\u7406\u7b49\u529f\u80fd\u3002\n\nIBM Intelligent Operations Center\u548cIBM Water Operations for Waternamics\u4e2d\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u5728\u9ed8\u8ba4\u60c5\u51b5\u4e0b\u7a0b\u5e8f\u672a\u80fd\u8981\u6c42\u7528\u6237\u4f7f\u7528\u5f3a\u5ea6\u8f83\u9ad8\u7684\u5bc6\u7801\uff0c\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u66b4\u529b\u7834\u89e3\u653b\u51fb\u5229\u7528\u8be5\u6f0f\u6d1e\u83b7\u53d6\u7528\u6237\u5bc6\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.ibm.com/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-25501",
  "openTime": "2019-08-02",
  "products": {
    "product": [
      "IBM Intelligent Operations Center \u003e=5.1.0\uff0c\u003c=5.2.0",
      "IBM Intelligent Operations Center for Emergency Management \u003e=5.1.0\uff0c\u003c=5.1.0.6",
      "IBM Water Operations for Waternamics \u003e=5.1.0\uff0c\u003c=5.2.1.1"
    ]
  },
  "referenceLink": "https://www.ibm.com/support/docview.wss?uid=ibm10880213\r\nhttps://exchange.xforce.ibmcloud.com/vulnerabilities/157012",
  "serverity": "\u4e2d",
  "submitTime": "2019-06-03",
  "title": "IBM Water Operations for Waternamics\u548cIBM Intelligent Operations Center\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2019-25501\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.