CNVD-2017-07530

Vulnerability from cnvd - Published: 2017-05-26
VLAI
Title
IBM Business Process Manager开放重定向漏洞
Description
IBM Business Process Manager(BPM)是美国IBM公司的一套综合的业务流程管理平台。该平台为业务的流程建模、组装、监控和部署提供了一系列的相关工具。 IBM Business Process Manager中存在开放重定向漏洞。远程攻击者可通过诱使用户访问特制的Web站点利用该漏洞将用户重定向到恶意的Web站点,实施钓鱼攻击,获取敏感信息。
Severity
高
Patch Name
IBM Business Process Manager开放重定向漏洞的补丁
Patch Description
IBM Business Process Manager(BPM)是美国IBM公司的一套综合的业务流程管理平台。该平台为业务的流程建模、组装、监控和部署提供了一系列的相关工具。 IBM Business Process Manager中存在开放重定向漏洞。远程攻击者可通过诱使用户访问特制的Web站点利用该漏洞将用户重定向到恶意的Web站点,实施钓鱼攻击,获取敏感信息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已经发布了升级补丁以修复此安全问题,补丁获取链接: http://www-01.ibm.com/support/docview.wss?uid=swg22000253

Reference
http://www-01.ibm.com/support/docview.wss?uid=swg22000253
Impacted products
Name
['IBM Business Process Manager >=8.0.0.0,<=8.0.1.3', 'IBM Business Process Manager >=8.5.0.0,<=8.5.0.2', 'IBM Business Process Manager 8.5.5.0', 'IBM Business Process Manager >=8.5.6.0,<=8.5.6.0 CF2', 'IBM Business Process Manager >=8.5.7.0,<=8.5.7.0 Cumulative Fix 2016.12', 'IBM Business Process Manager 7.5.0.0 through V7.5.1.2']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "98561"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-1159"
    }
  },
  "description": "IBM Business Process Manager\uff08BPM\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u7efc\u5408\u7684\u4e1a\u52a1\u6d41\u7a0b\u7ba1\u7406\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u4e3a\u4e1a\u52a1\u7684\u6d41\u7a0b\u5efa\u6a21\u3001\u7ec4\u88c5\u3001\u76d1\u63a7\u548c\u90e8\u7f72\u63d0\u4f9b\u4e86\u4e00\u7cfb\u5217\u7684\u76f8\u5173\u5de5\u5177\u3002\r\n\r\nIBM Business Process Manager\u4e2d\u5b58\u5728\u5f00\u653e\u91cd\u5b9a\u5411\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u8bf1\u4f7f\u7528\u6237\u8bbf\u95ee\u7279\u5236\u7684Web\u7ad9\u70b9\u5229\u7528\u8be5\u6f0f\u6d1e\u5c06\u7528\u6237\u91cd\u5b9a\u5411\u5230\u6076\u610f\u7684Web\u7ad9\u70b9\uff0c\u5b9e\u65bd\u9493\u9c7c\u653b\u51fb\uff0c\u83b7\u53d6\u654f\u611f\u4fe1\u606f\u3002",
  "discovererName": "IBM",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u7ecf\u53d1\u5e03\u4e86\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6b64\u5b89\u5168\u95ee\u9898\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttp://www-01.ibm.com/support/docview.wss?uid=swg22000253",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-07530",
  "openTime": "2017-05-26",
  "patchDescription": "IBM Business Process Manager\uff08BPM\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u7efc\u5408\u7684\u4e1a\u52a1\u6d41\u7a0b\u7ba1\u7406\u5e73\u53f0\u3002\u8be5\u5e73\u53f0\u4e3a\u4e1a\u52a1\u7684\u6d41\u7a0b\u5efa\u6a21\u3001\u7ec4\u88c5\u3001\u76d1\u63a7\u548c\u90e8\u7f72\u63d0\u4f9b\u4e86\u4e00\u7cfb\u5217\u7684\u76f8\u5173\u5de5\u5177\u3002\r\n\r\nIBM Business Process Manager\u4e2d\u5b58\u5728\u5f00\u653e\u91cd\u5b9a\u5411\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u901a\u8fc7\u8bf1\u4f7f\u7528\u6237\u8bbf\u95ee\u7279\u5236\u7684Web\u7ad9\u70b9\u5229\u7528\u8be5\u6f0f\u6d1e\u5c06\u7528\u6237\u91cd\u5b9a\u5411\u5230\u6076\u610f\u7684Web\u7ad9\u70b9\uff0c\u5b9e\u65bd\u9493\u9c7c\u653b\u51fb\uff0c\u83b7\u53d6\u654f\u611f\u4fe1\u606f\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 Business Process Manager\u5f00\u653e\u91cd\u5b9a\u5411\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "IBM Business Process Manager \u003e=8.0.0.0\uff0c\u003c=8.0.1.3",
      "IBM Business Process Manager \u003e=8.5.0.0\uff0c\u003c=8.5.0.2",
      "IBM Business Process Manager 8.5.5.0",
      "IBM Business Process Manager \u003e=8.5.6.0\uff0c\u003c=8.5.6.0 CF2",
      "IBM Business Process Manager \u003e=8.5.7.0\uff0c\u003c=8.5.7.0 Cumulative Fix 2016.12",
      "IBM Business Process Manager 7.5.0.0 through V7.5.1.2"
    ]
  },
  "referenceLink": "http://www-01.ibm.com/support/docview.wss?uid=swg22000253",
  "serverity": "\u9ad8",
  "submitTime": "2017-05-24",
  "title": "IBM Business Process Manager\u5f00\u653e\u91cd\u5b9a\u5411\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.