CNVD-2016-03727

Vulnerability from cnvd - Published: 2016-06-01
VLAI
Title
IBM WebSphere eXtreme Scale HTTP响应拆分漏洞
Description
IBM WebSphere eXtreme Scale是美国IBM公司的一套分布式高速缓存解决方案。该方案提供高性能、可扩展的高速缓存框架和网格技术,可处理海量事务、降低数据库的性能限制等。 IBM WebSphere eXtreme Scale中存在HTTP响应拆分漏洞,该漏洞源于程序处理恶意请求时未能正确验证用户输入。远程攻击者可借助特制的URL利用该漏洞注入包含Unicode字符的HTTP头,使服务器返回拆分响应信息。
Severity
中
Patch Name
IBM WebSphere eXtreme Scale HTTP响应拆分漏洞的补丁
Patch Description
IBM WebSphere eXtreme Scale是美国IBM公司的一套分布式高速缓存解决方案。该方案提供高性能、可扩展的高速缓存框架和网格技术,可处理海量事务、降低数据库的性能限制等。 IBM WebSphere eXtreme Scale中存在HTTP响应拆分漏洞,该漏洞源于程序处理恶意请求时未能正确验证用户输入。远程攻击者可借助特制的URL利用该漏洞注入包含Unicode字符的HTTP头,使服务器返回拆分响应信息。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

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

Reference
http://www.ibm.com/support/docview.wss?uid=swg21982963 http://www.ibm.com/support/docview.wss?uid=swg21983036 http://www.auscert.org.au/./render.html?it=35178
Impacted products
Name
['IBM WebSphere eXtreme Scale 7.1.0', 'IBM WebSphere eXtreme Scale 7.1.1', 'IBM WebSphere eXtreme Scale 8.5', 'IBM WebSphere eXtreme Scale 8.6']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-0400"
    }
  },
  "description": "IBM WebSphere eXtreme Scale\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u5206\u5e03\u5f0f\u9ad8\u901f\u7f13\u5b58\u89e3\u51b3\u65b9\u6848\u3002\u8be5\u65b9\u6848\u63d0\u4f9b\u9ad8\u6027\u80fd\u3001\u53ef\u6269\u5c55\u7684\u9ad8\u901f\u7f13\u5b58\u6846\u67b6\u548c\u7f51\u683c\u6280\u672f\uff0c\u53ef\u5904\u7406\u6d77\u91cf\u4e8b\u52a1\u3001\u964d\u4f4e\u6570\u636e\u5e93\u7684\u6027\u80fd\u9650\u5236\u7b49\u3002\r\n\r\nIBM WebSphere eXtreme Scale\u4e2d\u5b58\u5728HTTP\u54cd\u5e94\u62c6\u5206\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u5904\u7406\u6076\u610f\u8bf7\u6c42\u65f6\u672a\u80fd\u6b63\u786e\u9a8c\u8bc1\u7528\u6237\u8f93\u5165\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u501f\u52a9\u7279\u5236\u7684URL\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u5305\u542bUnicode\u5b57\u7b26\u7684HTTP\u5934\uff0c\u4f7f\u670d\u52a1\u5668\u8fd4\u56de\u62c6\u5206\u54cd\u5e94\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=swg21983036",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2016-03727",
  "openTime": "2016-06-01",
  "patchDescription": "IBM WebSphere eXtreme Scale\u662f\u7f8e\u56fdIBM\u516c\u53f8\u7684\u4e00\u5957\u5206\u5e03\u5f0f\u9ad8\u901f\u7f13\u5b58\u89e3\u51b3\u65b9\u6848\u3002\u8be5\u65b9\u6848\u63d0\u4f9b\u9ad8\u6027\u80fd\u3001\u53ef\u6269\u5c55\u7684\u9ad8\u901f\u7f13\u5b58\u6846\u67b6\u548c\u7f51\u683c\u6280\u672f\uff0c\u53ef\u5904\u7406\u6d77\u91cf\u4e8b\u52a1\u3001\u964d\u4f4e\u6570\u636e\u5e93\u7684\u6027\u80fd\u9650\u5236\u7b49\u3002\r\n\r\nIBM WebSphere eXtreme Scale\u4e2d\u5b58\u5728HTTP\u54cd\u5e94\u62c6\u5206\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7a0b\u5e8f\u5904\u7406\u6076\u610f\u8bf7\u6c42\u65f6\u672a\u80fd\u6b63\u786e\u9a8c\u8bc1\u7528\u6237\u8f93\u5165\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u501f\u52a9\u7279\u5236\u7684URL\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u5305\u542bUnicode\u5b57\u7b26\u7684HTTP\u5934\uff0c\u4f7f\u670d\u52a1\u5668\u8fd4\u56de\u62c6\u5206\u54cd\u5e94\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 WebSphere eXtreme Scale HTTP\u54cd\u5e94\u62c6\u5206\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "IBM WebSphere eXtreme Scale 7.1.0",
      "IBM WebSphere eXtreme Scale 7.1.1",
      "IBM WebSphere eXtreme Scale  8.5",
      "IBM WebSphere eXtreme Scale  8.6"
    ]
  },
  "referenceLink": "http://www.ibm.com/support/docview.wss?uid=swg21982963\r\nhttp://www.ibm.com/support/docview.wss?uid=swg21983036\r\nhttp://www.auscert.org.au/./render.html?it=35178",
  "serverity": "\u4e2d",
  "submitTime": "2016-05-31",
  "title": "IBM WebSphere eXtreme Scale HTTP\u54cd\u5e94\u62c6\u5206\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.