CNVD-2018-24091

Vulnerability from cnvd - Published: 2018-11-27
VLAI
Title
TIBCO Rendezvous跨站请求伪造漏洞
Description
TIBCO Rendezvous是美国TIBCO软件公司的一款可帮助用户快速构建和部署大规模分布式应用的中间件产品。 TIBCO Rendezvous中的多个组件(Rendezvous Routing Daemon (rvrd)、Rendezvous Secure Routing Daemon (rvrsd)、Rendezvous Secure Daemon (rvsd)、Rendezvous Cache (rvcache)及Rendezvous Daemon Manager (rvdm))存在跨站请求伪造漏洞。攻击者可利用该漏洞重新配置所有消息。
Severity
高
Patch Name
TIBCO Rendezvous跨站请求伪造漏洞的补丁
Patch Description
TIBCO Rendezvous是美国TIBCO软件公司的一款可帮助用户快速构建和部署大规模分布式应用的中间件产品。 TIBCO Rendezvous中的多个组件(Rendezvous Routing Daemon (rvrd)、Rendezvous Secure Routing Daemon (rvrsd)、Rendezvous Secure Daemon (rvsd)、Rendezvous Cache (rvcache)及Rendezvous Daemon Manager (rvdm))存在跨站请求伪造漏洞。攻击者可利用该漏洞重新配置所有消息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://www.tibco.com/support/advisories/2018/11/tibco-security-advisory-november-6-2018-tibco-rendezvous

Reference
https://www.tibco.com/support/advisories/2018/11/tibco-security-advisory-november-6-2018-tibco-rendezvous
Impacted products
Name
['TIBCO Rendezvous <=8.4.5', 'TIBCO Rendezvous Developer Edition <=8.4.5', 'TIBCO Rendezvous for z/Linux versions <=8.4.5', 'TIBCO Rendezvous for z/OS <=8.4.5', 'TIBCO Rendezvous Network Server <=1.1.2', 'TIBCO Substation ES versions <=2.12.0']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "105871"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2018-12414"
    }
  },
  "description": "TIBCO Rendezvous\u662f\u7f8e\u56fdTIBCO\u8f6f\u4ef6\u516c\u53f8\u7684\u4e00\u6b3e\u53ef\u5e2e\u52a9\u7528\u6237\u5feb\u901f\u6784\u5efa\u548c\u90e8\u7f72\u5927\u89c4\u6a21\u5206\u5e03\u5f0f\u5e94\u7528\u7684\u4e2d\u95f4\u4ef6\u4ea7\u54c1\u3002\n\nTIBCO Rendezvous\u4e2d\u7684\u591a\u4e2a\u7ec4\u4ef6\uff08Rendezvous Routing Daemon (rvrd)\u3001Rendezvous Secure Routing Daemon (rvrsd)\u3001Rendezvous Secure Daemon (rvsd)\u3001Rendezvous Cache (rvcache)\u53caRendezvous Daemon Manager (rvdm)\uff09\u5b58\u5728\u8de8\u7ad9\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u91cd\u65b0\u914d\u7f6e\u6240\u6709\u6d88\u606f\u3002",
  "discovererName": "TIBCO",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://www.tibco.com/support/advisories/2018/11/tibco-security-advisory-november-6-2018-tibco-rendezvous",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-24091",
  "openTime": "2018-11-27",
  "patchDescription": "TIBCO Rendezvous\u662f\u7f8e\u56fdTIBCO\u8f6f\u4ef6\u516c\u53f8\u7684\u4e00\u6b3e\u53ef\u5e2e\u52a9\u7528\u6237\u5feb\u901f\u6784\u5efa\u548c\u90e8\u7f72\u5927\u89c4\u6a21\u5206\u5e03\u5f0f\u5e94\u7528\u7684\u4e2d\u95f4\u4ef6\u4ea7\u54c1\u3002\r\n\r\nTIBCO Rendezvous\u4e2d\u7684\u591a\u4e2a\u7ec4\u4ef6\uff08Rendezvous Routing Daemon (rvrd)\u3001Rendezvous Secure Routing Daemon (rvrsd)\u3001Rendezvous Secure Daemon (rvsd)\u3001Rendezvous Cache (rvcache)\u53caRendezvous Daemon Manager (rvdm)\uff09\u5b58\u5728\u8de8\u7ad9\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u91cd\u65b0\u914d\u7f6e\u6240\u6709\u6d88\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": "TIBCO Rendezvous\u8de8\u7ad9\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "TIBCO Rendezvous \u003c=8.4.5",
      "TIBCO Rendezvous Developer Edition \u003c=8.4.5",
      "TIBCO Rendezvous for z/Linux versions \u003c=8.4.5",
      "TIBCO Rendezvous for z/OS \u003c=8.4.5",
      "TIBCO Rendezvous Network Server \u003c=1.1.2",
      "TIBCO Substation ES versions \u003c=2.12.0"
    ]
  },
  "referenceLink": "https://www.tibco.com/support/advisories/2018/11/tibco-security-advisory-november-6-2018-tibco-rendezvous",
  "serverity": "\u9ad8",
  "submitTime": "2018-11-08",
  "title": "TIBCO Rendezvous\u8de8\u7ad9\u8bf7\u6c42\u4f2a\u9020\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.