CNVD-2015-03567

Vulnerability from cnvd - Published: 2015-06-04
VLAI
Title
IBM Rational Requirements Composer和Rational DOORS Next Generation本地权限提升漏洞
Description
IBM Rational Requirements Composer和Rational DOORS Next Generation(RDNG)是美国IBM公司的需求管理解决方案。 IBM Rational Requirements Composer和RDNG中使用的WebSphere Application Server和LTPA单点登录共同使用时,程序在LTPA令牌过期后没有终止Requirements Management(RM)会话,存在安全漏洞,允许攻击者绕过限制进行访问。
Severity
低
Patch Name
IBM Rational Requirements Composer和Rational DOORS Next Generation本地权限提升漏洞的补丁
Patch Description
IBM Rational Requirements Composer和Rational DOORS Next Generation(RDNG)是美国IBM公司的需求管理解决方案。IBM Rational Requirements Composer和RDNG中使用的WebSphere Application Server和LTPA单点登录共同使用时,程序在LTPA令牌过期后没有终止Requirements Management(RM)会话,存在安全漏洞,允许攻击者绕过限制进行访问。目前,厂商已经发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

用户可参考如下厂商提供的安全公告获取补丁以修复该漏洞: http://www-01.ibm.com/support/docview.wss?uid=swg21903761

Reference
http://www-01.ibm.com/support/docview.wss?uid=swg21903761
Impacted products
Name
['IBM Rational Requirements Composer 3.0', 'IBM Rational Requirements Composer 3.0.1', 'IBM Rational Requirements Composer 3.0.1.1-3.0.1.6', 'IBM Rational Requirements Composer 4.0', 'IBM Rational Requirements Composer 4.0.0-4.0.7', 'IBM Rational Requirements Composer 4.0.0.1', 'IBM Rational Requirements Composer 4.0.0.2', 'IBM Rational DOORS Next Generation 4.0.0-4.0.7', 'IBM Rational DOORS Next Generation 5.0', 'IBM Rational DOORS Next Generation 5.0.1', 'IBM Rational DOORS Next Generation 5.0.2']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "74910"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-0121"
    }
  },
  "description": "IBM Rational Requirements Composer\u548cRational DOORS Next Generation\uff08RDNG\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u9700\u6c42\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002\r\n\r\nIBM Rational Requirements Composer\u548cRDNG\u4e2d\u4f7f\u7528\u7684WebSphere Application Server\u548cLTPA\u5355\u70b9\u767b\u5f55\u5171\u540c\u4f7f\u7528\u65f6\uff0c\u7a0b\u5e8f\u5728LTPA\u4ee4\u724c\u8fc7\u671f\u540e\u6ca1\u6709\u7ec8\u6b62Requirements Management(RM)\u4f1a\u8bdd\uff0c\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u5141\u8bb8\u653b\u51fb\u8005\u7ed5\u8fc7\u9650\u5236\u8fdb\u884c\u8bbf\u95ee\u3002",
  "discovererName": "IBM",
  "formalWay": "\u7528\u6237\u53ef\u53c2\u8003\u5982\u4e0b\u5382\u5546\u63d0\u4f9b\u7684\u5b89\u5168\u516c\u544a\u83b7\u53d6\u8865\u4e01\u4ee5\u4fee\u590d\u8be5\u6f0f\u6d1e\uff1a\r\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21903761",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2015-03567",
  "openTime": "2015-06-04",
  "patchDescription": "IBM Rational Requirements Composer\u548cRational DOORS Next Generation\uff08RDNG\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u9700\u6c42\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002IBM Rational Requirements Composer\u548cRDNG\u4e2d\u4f7f\u7528\u7684WebSphere Application Server\u548cLTPA\u5355\u70b9\u767b\u5f55\u5171\u540c\u4f7f\u7528\u65f6\uff0c\u7a0b\u5e8f\u5728LTPA\u4ee4\u724c\u8fc7\u671f\u540e\u6ca1\u6709\u7ec8\u6b62Requirements Management(RM)\u4f1a\u8bdd\uff0c\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\uff0c\u5141\u8bb8\u653b\u51fb\u8005\u7ed5\u8fc7\u9650\u5236\u8fdb\u884c\u8bbf\u95ee\u3002\u76ee\u524d\uff0c\u5382\u5546\u5df2\u7ecf\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "IBM Rational Requirements Composer\u548cRational DOORS Next Generation\u672c\u5730\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "IBM Rational Requirements Composer 3.0",
      "IBM Rational Requirements Composer 3.0.1",
      "IBM Rational Requirements Composer 3.0.1.1-3.0.1.6",
      "IBM Rational Requirements Composer 4.0",
      "IBM Rational Requirements Composer 4.0.0-4.0.7",
      "IBM Rational Requirements Composer 4.0.0.1",
      "IBM Rational Requirements Composer 4.0.0.2",
      "IBM  Rational DOORS Next Generation 4.0.0-4.0.7",
      "IBM  Rational DOORS Next Generation 5.0",
      "IBM  Rational DOORS Next Generation 5.0.1",
      "IBM  Rational DOORS Next Generation 5.0.2"
    ]
  },
  "referenceLink": "http://www-01.ibm.com/support/docview.wss?uid=swg21903761",
  "serverity": "\u4f4e",
  "submitTime": "2015-06-01",
  "title": "IBM Rational Requirements Composer\u548cRational DOORS Next Generation\u672c\u5730\u6743\u9650\u63d0\u5347\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.