CNVD-2015-07518

Vulnerability from cnvd - Published: 2015-11-13
VLAI
Title
SAP HANA DB远程跟踪泄露漏洞
Description
SAP HANA DB是德国思爱普(SAP)公司的一个基于行和列的内存数据库。该数据库提供针对多维数据进行快速查询、过滤掉杂乱的无用数据、同步执行多项查询等功能。 SAP HANA DB 1.00.73.00.389160(NewDB100_REL)版本中的Web Dispatcher服务存在安全漏洞。远程攻击者可利用该漏洞读取网络调度和安全跟踪文件,获取密码。
Severity
Patch Name
SAP HANA DB远程跟踪披露漏洞的补丁
Patch Description
SAP HANA DB是德国思爱普(SAP)公司的一个基于行和列的内存数据库。该数据库提供针对多维数据进行快速查询、过滤掉杂乱的无用数据、同步执行多项查询等功能。 SAP HANA DB 1.00.73.00.389160(NewDB100_REL)版本中的Web Dispatcher服务存在安全漏洞。远程攻击者可利用该漏洞读取网络调度和安全跟踪文件,获取密码。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

用户可联系供应商获得补丁信息: http://www.sap.com

Reference
http://www.onapsis.com/research/security-advisories/SAP_HANA_Remote_Trace_Disclosure http://packetstormsecurity.com/files/134283/SAP-HANA-Remote-Trace-Disclosure.html http://seclists.org/fulldisclosure/2015/Nov/37
Impacted products
Name
SAP HANA DB 1.00.73.00.389160
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2015-7991"
    }
  },
  "description": "SAP HANA DB\u662f\u5fb7\u56fd\u601d\u7231\u666e\uff08SAP\uff09\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8e\u884c\u548c\u5217\u7684\u5185\u5b58\u6570\u636e\u5e93\u3002\u8be5\u6570\u636e\u5e93\u63d0\u4f9b\u9488\u5bf9\u591a\u7ef4\u6570\u636e\u8fdb\u884c\u5feb\u901f\u67e5\u8be2\u3001\u8fc7\u6ee4\u6389\u6742\u4e71\u7684\u65e0\u7528\u6570\u636e\u3001\u540c\u6b65\u6267\u884c\u591a\u9879\u67e5\u8be2\u7b49\u529f\u80fd\u3002\r\n\r\nSAP HANA DB 1.00.73.00.389160(NewDB100_REL)\u7248\u672c\u4e2d\u7684Web Dispatcher\u670d\u52a1\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u8bfb\u53d6\u7f51\u7edc\u8c03\u5ea6\u548c\u5b89\u5168\u8ddf\u8e2a\u6587\u4ef6\uff0c\u83b7\u53d6\u5bc6\u7801\u3002",
  "discovererName": "Juan Perez-Etchegoyen and Sergio Abraham",
  "formalWay": "\u7528\u6237\u53ef\u8054\u7cfb\u4f9b\u5e94\u5546\u83b7\u5f97\u8865\u4e01\u4fe1\u606f\uff1a\r\nhttp://www.sap.com",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2015-07518",
  "openTime": "2015-11-13",
  "patchDescription": "SAP HANA DB\u662f\u5fb7\u56fd\u601d\u7231\u666e\uff08SAP\uff09\u516c\u53f8\u7684\u4e00\u4e2a\u57fa\u4e8e\u884c\u548c\u5217\u7684\u5185\u5b58\u6570\u636e\u5e93\u3002\u8be5\u6570\u636e\u5e93\u63d0\u4f9b\u9488\u5bf9\u591a\u7ef4\u6570\u636e\u8fdb\u884c\u5feb\u901f\u67e5\u8be2\u3001\u8fc7\u6ee4\u6389\u6742\u4e71\u7684\u65e0\u7528\u6570\u636e\u3001\u540c\u6b65\u6267\u884c\u591a\u9879\u67e5\u8be2\u7b49\u529f\u80fd\u3002\r\nSAP HANA DB 1.00.73.00.389160(NewDB100_REL)\u7248\u672c\u4e2d\u7684Web Dispatcher\u670d\u52a1\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u8bfb\u53d6\u7f51\u7edc\u8c03\u5ea6\u548c\u5b89\u5168\u8ddf\u8e2a\u6587\u4ef6\uff0c\u83b7\u53d6\u5bc6\u7801\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": "SAP HANA DB\u8fdc\u7a0b\u8ddf\u8e2a\u62ab\u9732\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "SAP HANA DB 1.00.73.00.389160"
  },
  "referenceLink": "http://www.onapsis.com/research/security-advisories/SAP_HANA_Remote_Trace_Disclosure \r\nhttp://packetstormsecurity.com/files/134283/SAP-HANA-Remote-Trace-Disclosure.html \r\nhttp://seclists.org/fulldisclosure/2015/Nov/37",
  "serverity": "\u4e2d",
  "submitTime": "2015-11-12",
  "title": "SAP HANA DB\u8fdc\u7a0b\u8ddf\u8e2a\u6cc4\u9732\u6f0f\u6d1e"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…