CNVD-2016-06746

Vulnerability from cnvd - Published: 2016-08-26
VLAI
Title
VMware Identity Manager and vRealize Automation本地权限提升漏洞
Description
VMware Identity Manager和vRealize Automation都是美国威睿(VMware)公司的产品。前者是一款可提供应用调配、自助服务目录、为SaaS、Web、云计算和原生移动应用提供单点登录 (SSO) 等功能的“身份认证即服务”(IDaaS) 产品,后者是一套支持自动交付个性化基础架构,跨多供应商、混合云基础架构进行部署,简化应用发布自动化和持续交付等的云计算自动化软件。 VMware Identity Manager 2.0版本和vRealize Automation 7.0版本中存在本地权限提升漏洞。本地攻击者可利用该漏洞在受影响的系统中获取提升的权限。
Severity
高
Patch Name
VMware Identity Manager and vRealize Automation本地权限提升漏洞的补丁
Patch Description
VMware Identity Manager和vRealize Automation都是美国威睿(VMware)公司的产品。前者是一款可提供应用调配、自助服务目录、为SaaS、Web、云计算和原生移动应用提供单点登录 (SSO) 等功能的“身份认证即服务”(IDaaS) 产品,后者是一套支持自动交付个性化基础架构,跨多供应商、混合云基础架构进行部署,简化应用发布自动化和持续交付等的云计算自动化软件。 VMware Identity Manager 2.0版本和vRealize Automation 7.0版本中存在本地权限提升漏洞。本地攻击者可利用该漏洞在受影响的系统中获取提升的权限。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已经发布了升级补丁以修复此安全问题,补丁获取链接: http://www.vmware.com/security/advisories/VMSA-2016-0013.html

Reference
http://www.securityfocus.com/bid/92608
Impacted products
Name
['VMware vRealize Automation 7.0', 'VMware Identity Manager 2.0']
Show details on source website

{
  "bids": {
    "bid": {
      "bidNumber": "92608"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-5335"
    }
  },
  "description": "VMware Identity Manager\u548cvRealize Automation\u90fd\u662f\u7f8e\u56fd\u5a01\u777f\uff08VMware\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002\u524d\u8005\u662f\u4e00\u6b3e\u53ef\u63d0\u4f9b\u5e94\u7528\u8c03\u914d\u3001\u81ea\u52a9\u670d\u52a1\u76ee\u5f55\u3001\u4e3aSaaS\u3001Web\u3001\u4e91\u8ba1\u7b97\u548c\u539f\u751f\u79fb\u52a8\u5e94\u7528\u63d0\u4f9b\u5355\u70b9\u767b\u5f55 (SSO) \u7b49\u529f\u80fd\u7684\u201c\u8eab\u4efd\u8ba4\u8bc1\u5373\u670d\u52a1\u201d(IDaaS) \u4ea7\u54c1\uff0c\u540e\u8005\u662f\u4e00\u5957\u652f\u6301\u81ea\u52a8\u4ea4\u4ed8\u4e2a\u6027\u5316\u57fa\u7840\u67b6\u6784\uff0c\u8de8\u591a\u4f9b\u5e94\u5546\u3001\u6df7\u5408\u4e91\u57fa\u7840\u67b6\u6784\u8fdb\u884c\u90e8\u7f72\uff0c\u7b80\u5316\u5e94\u7528\u53d1\u5e03\u81ea\u52a8\u5316\u548c\u6301\u7eed\u4ea4\u4ed8\u7b49\u7684\u4e91\u8ba1\u7b97\u81ea\u52a8\u5316\u8f6f\u4ef6\u3002\r\n\r\nVMware Identity Manager 2.0\u7248\u672c\u548cvRealize Automation 7.0\u7248\u672c\u4e2d\u5b58\u5728\u672c\u5730\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u4e2d\u83b7\u53d6\u63d0\u5347\u7684\u6743\u9650\u3002",
  "discovererName": "VMware",
  "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.vmware.com/security/advisories/VMSA-2016-0013.html",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2016-06746",
  "openTime": "2016-08-26",
  "patchDescription": "VMware Identity Manager\u548cvRealize Automation\u90fd\u662f\u7f8e\u56fd\u5a01\u777f\uff08VMware\uff09\u516c\u53f8\u7684\u4ea7\u54c1\u3002\u524d\u8005\u662f\u4e00\u6b3e\u53ef\u63d0\u4f9b\u5e94\u7528\u8c03\u914d\u3001\u81ea\u52a9\u670d\u52a1\u76ee\u5f55\u3001\u4e3aSaaS\u3001Web\u3001\u4e91\u8ba1\u7b97\u548c\u539f\u751f\u79fb\u52a8\u5e94\u7528\u63d0\u4f9b\u5355\u70b9\u767b\u5f55 (SSO) \u7b49\u529f\u80fd\u7684\u201c\u8eab\u4efd\u8ba4\u8bc1\u5373\u670d\u52a1\u201d(IDaaS) \u4ea7\u54c1\uff0c\u540e\u8005\u662f\u4e00\u5957\u652f\u6301\u81ea\u52a8\u4ea4\u4ed8\u4e2a\u6027\u5316\u57fa\u7840\u67b6\u6784\uff0c\u8de8\u591a\u4f9b\u5e94\u5546\u3001\u6df7\u5408\u4e91\u57fa\u7840\u67b6\u6784\u8fdb\u884c\u90e8\u7f72\uff0c\u7b80\u5316\u5e94\u7528\u53d1\u5e03\u81ea\u52a8\u5316\u548c\u6301\u7eed\u4ea4\u4ed8\u7b49\u7684\u4e91\u8ba1\u7b97\u81ea\u52a8\u5316\u8f6f\u4ef6\u3002\r\n\r\nVMware Identity Manager 2.0\u7248\u672c\u548cvRealize Automation 7.0\u7248\u672c\u4e2d\u5b58\u5728\u672c\u5730\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\u3002\u672c\u5730\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5728\u53d7\u5f71\u54cd\u7684\u7cfb\u7edf\u4e2d\u83b7\u53d6\u63d0\u5347\u7684\u6743\u9650\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": "VMware Identity Manager and vRealize Automation\u672c\u5730\u6743\u9650\u63d0\u5347\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "VMware vRealize Automation 7.0",
      "VMware Identity Manager 2.0"
    ]
  },
  "referenceLink": "http://www.securityfocus.com/bid/92608",
  "serverity": "\u9ad8",
  "submitTime": "2016-08-25",
  "title": "VMware Identity Manager and vRealize Automation\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.