CNVD-2022-56975

Vulnerability from cnvd - Published: 2022-08-16
VLAI
Title
IBM Engineering Lifecycle Optimization信息泄露漏洞
Description
IBM Engineering Lifecycle Optimization(ELO)是美国IBM公司的工程生命周期管理 (ELM) 产品组合的扩展。它们可以更轻松地收集和分析整个开发环境中的数据,以做出更好的决策。自动化报告以确保整个组织拥有优化开发所需的信息,定义可以帮助您的扩展团队采用和遵循最佳实践的流程,与第三方工具接口以自定义您的开发环境。 IBM Engineering Lifecycle Optimization存在信息泄露漏洞,该漏洞源于HTTP GET请求输出过多敏感信息,经过身份验证的攻击者可通过HTTP GET请求获得高度敏感的信息。
Severity
中
Patch Name
IBM Engineering Lifecycle Optimization信息泄露漏洞的补丁
Patch Description
IBM Engineering Lifecycle Optimization(ELO)是美国IBM公司的工程生命周期管理 (ELM) 产品组合的扩展。它们可以更轻松地收集和分析整个开发环境中的数据,以做出更好的决策。自动化报告以确保整个组织拥有优化开发所需的信息,定义可以帮助您的扩展团队采用和遵循最佳实践的流程,与第三方工具接口以自定义您的开发环境。 IBM Engineering Lifecycle Optimization存在信息泄露漏洞,该漏洞源于HTTP GET请求输出过多敏感信息,经过身份验证的攻击者可通过HTTP GET请求获得高度敏感的信息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://www.ibm.com/support/pages/node/6603355

Reference
https://nvd.nist.gov/vuln/detail/CVE-2021-39019
Impacted products
Name
['IBM Engineering Lifecycle Optimization 6.0.6', 'IBM Engineering Lifecycle Optimization 6.0.6.1', 'IBM Engineering Lifecycle Optimization 7.0', 'IBM Engineering Lifecycle Optimization 7.0.1', 'IBM Engineering Lifecycle Optimization 7.0.2']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-39019",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2021-39019"
    }
  },
  "description": "IBM Engineering Lifecycle Optimization\uff08ELO\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u5de5\u7a0b\u751f\u547d\u5468\u671f\u7ba1\u7406 (ELM) \u4ea7\u54c1\u7ec4\u5408\u7684\u6269\u5c55\u3002\u5b83\u4eec\u53ef\u4ee5\u66f4\u8f7b\u677e\u5730\u6536\u96c6\u548c\u5206\u6790\u6574\u4e2a\u5f00\u53d1\u73af\u5883\u4e2d\u7684\u6570\u636e\uff0c\u4ee5\u505a\u51fa\u66f4\u597d\u7684\u51b3\u7b56\u3002\u81ea\u52a8\u5316\u62a5\u544a\u4ee5\u786e\u4fdd\u6574\u4e2a\u7ec4\u7ec7\u62e5\u6709\u4f18\u5316\u5f00\u53d1\u6240\u9700\u7684\u4fe1\u606f\uff0c\u5b9a\u4e49\u53ef\u4ee5\u5e2e\u52a9\u60a8\u7684\u6269\u5c55\u56e2\u961f\u91c7\u7528\u548c\u9075\u5faa\u6700\u4f73\u5b9e\u8df5\u7684\u6d41\u7a0b\uff0c\u4e0e\u7b2c\u4e09\u65b9\u5de5\u5177\u63a5\u53e3\u4ee5\u81ea\u5b9a\u4e49\u60a8\u7684\u5f00\u53d1\u73af\u5883\u3002\n\nIBM Engineering Lifecycle Optimization\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eHTTP GET\u8bf7\u6c42\u8f93\u51fa\u8fc7\u591a\u654f\u611f\u4fe1\u606f\uff0c\u7ecf\u8fc7\u8eab\u4efd\u9a8c\u8bc1\u7684\u653b\u51fb\u8005\u53ef\u901a\u8fc7HTTP GET\u8bf7\u6c42\u83b7\u5f97\u9ad8\u5ea6\u654f\u611f\u7684\u4fe1\u606f\u3002",
  "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/pages/node/6603355",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-56975",
  "openTime": "2022-08-16",
  "patchDescription": "IBM Engineering Lifecycle Optimization\uff08ELO\uff09\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u5de5\u7a0b\u751f\u547d\u5468\u671f\u7ba1\u7406 (ELM) \u4ea7\u54c1\u7ec4\u5408\u7684\u6269\u5c55\u3002\u5b83\u4eec\u53ef\u4ee5\u66f4\u8f7b\u677e\u5730\u6536\u96c6\u548c\u5206\u6790\u6574\u4e2a\u5f00\u53d1\u73af\u5883\u4e2d\u7684\u6570\u636e\uff0c\u4ee5\u505a\u51fa\u66f4\u597d\u7684\u51b3\u7b56\u3002\u81ea\u52a8\u5316\u62a5\u544a\u4ee5\u786e\u4fdd\u6574\u4e2a\u7ec4\u7ec7\u62e5\u6709\u4f18\u5316\u5f00\u53d1\u6240\u9700\u7684\u4fe1\u606f\uff0c\u5b9a\u4e49\u53ef\u4ee5\u5e2e\u52a9\u60a8\u7684\u6269\u5c55\u56e2\u961f\u91c7\u7528\u548c\u9075\u5faa\u6700\u4f73\u5b9e\u8df5\u7684\u6d41\u7a0b\uff0c\u4e0e\u7b2c\u4e09\u65b9\u5de5\u5177\u63a5\u53e3\u4ee5\u81ea\u5b9a\u4e49\u60a8\u7684\u5f00\u53d1\u73af\u5883\u3002\r\n\r\nIBM Engineering Lifecycle Optimization\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eHTTP GET\u8bf7\u6c42\u8f93\u51fa\u8fc7\u591a\u654f\u611f\u4fe1\u606f\uff0c\u7ecf\u8fc7\u8eab\u4efd\u9a8c\u8bc1\u7684\u653b\u51fb\u8005\u53ef\u901a\u8fc7HTTP GET\u8bf7\u6c42\u83b7\u5f97\u9ad8\u5ea6\u654f\u611f\u7684\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 Engineering Lifecycle Optimization\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "IBM Engineering Lifecycle Optimization 6.0.6",
      "IBM Engineering Lifecycle Optimization 6.0.6.1",
      "IBM Engineering Lifecycle Optimization 7.0",
      "IBM Engineering Lifecycle Optimization 7.0.1",
      "IBM Engineering Lifecycle Optimization 7.0.2"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2021-39019",
  "serverity": "\u4e2d",
  "submitTime": "2022-07-18",
  "title": "IBM Engineering Lifecycle Optimization\u4fe1\u606f\u6cc4\u9732\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.