CNVD-2020-03755

Vulnerability from cnvd - Published: 2020-02-05
VLAI
Title
Cisco Unified Communications Manager信息泄露漏洞(CNVD-2020-03755)
Description
Cisco Unified Communications Manager是Cisco协作平台的核心,可让一个人通过任何设备、在任何操作系统上通过语音、视频、消息轻松与他人进行通信。 Cisco Unified Communications Manager 10.5(2)(SU9)、11.5(1)(SU6)、12.0(1)(SU3)、12.5(1)(SU1)及更早版本的基于Web的管理界面存在信息泄露漏洞。该漏洞源于基于Web的管理界面对用户提供的输入保护不足。远程认证攻击者可利用该漏洞查看敏感信息或进行进一步的攻击。
Severity
中
Patch Name
Cisco Unified Communications Manager信息泄露漏洞(CNVD-2020-03755)的补丁
Patch Description
Cisco Unified Communications Manager是Cisco协作平台的核心,可让一个人通过任何设备、在任何操作系统上通过语音、视频、消息轻松与他人进行通信。 Cisco Unified Communications Manager 10.5(2)(SU9)、11.5(1)(SU6)、12.0(1)(SU3)、12.5(1)(SU1)及更早版本的基于Web的管理界面存在信息泄露漏洞。该漏洞源于基于Web的管理界面对用户提供的输入保护不足。远程认证攻击者可利用该漏洞查看敏感信息或进行进一步的攻击。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

厂商已发布了漏洞修复程序,请及时关注更新: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200122-cuc-info-disclosure

Reference
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200122-cuc-info-disclosure
Impacted products
Name
['Cisco Cisco Unified Communications Manager <=10.5(2)(SU9)', 'Cisco Cisco Unified Communications Manager <=11.5(1)(SU6)', 'Cisco Cisco Unified Communications Manager <=12.0(1)(SU3)', 'Cisco Cisco Unified Communications Manager <=12.5(1)(SU1)']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-15963",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2019-15963"
    }
  },
  "description": "Cisco Unified Communications Manager\u662fCisco\u534f\u4f5c\u5e73\u53f0\u7684\u6838\u5fc3\uff0c\u53ef\u8ba9\u4e00\u4e2a\u4eba\u901a\u8fc7\u4efb\u4f55\u8bbe\u5907\u3001\u5728\u4efb\u4f55\u64cd\u4f5c\u7cfb\u7edf\u4e0a\u901a\u8fc7\u8bed\u97f3\u3001\u89c6\u9891\u3001\u6d88\u606f\u8f7b\u677e\u4e0e\u4ed6\u4eba\u8fdb\u884c\u901a\u4fe1\u3002\n\nCisco Unified Communications Manager 10.5(2)(SU9)\u300111.5(1)(SU6)\u300112.0(1)(SU3)\u300112.5(1)(SU1)\u53ca\u66f4\u65e9\u7248\u672c\u7684\u57fa\u4e8eWeb\u7684\u7ba1\u7406\u754c\u9762\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u57fa\u4e8eWeb\u7684\u7ba1\u7406\u754c\u9762\u5bf9\u7528\u6237\u63d0\u4f9b\u7684\u8f93\u5165\u4fdd\u62a4\u4e0d\u8db3\u3002\u8fdc\u7a0b\u8ba4\u8bc1\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u67e5\u770b\u654f\u611f\u4fe1\u606f\u6216\u8fdb\u884c\u8fdb\u4e00\u6b65\u7684\u653b\u51fb\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://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200122-cuc-info-disclosure",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-03755",
  "openTime": "2020-02-05",
  "patchDescription": "Cisco Unified Communications Manager\u662fCisco\u534f\u4f5c\u5e73\u53f0\u7684\u6838\u5fc3\uff0c\u53ef\u8ba9\u4e00\u4e2a\u4eba\u901a\u8fc7\u4efb\u4f55\u8bbe\u5907\u3001\u5728\u4efb\u4f55\u64cd\u4f5c\u7cfb\u7edf\u4e0a\u901a\u8fc7\u8bed\u97f3\u3001\u89c6\u9891\u3001\u6d88\u606f\u8f7b\u677e\u4e0e\u4ed6\u4eba\u8fdb\u884c\u901a\u4fe1\u3002\r\n\r\nCisco Unified Communications Manager 10.5(2)(SU9)\u300111.5(1)(SU6)\u300112.0(1)(SU3)\u300112.5(1)(SU1)\u53ca\u66f4\u65e9\u7248\u672c\u7684\u57fa\u4e8eWeb\u7684\u7ba1\u7406\u754c\u9762\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u57fa\u4e8eWeb\u7684\u7ba1\u7406\u754c\u9762\u5bf9\u7528\u6237\u63d0\u4f9b\u7684\u8f93\u5165\u4fdd\u62a4\u4e0d\u8db3\u3002\u8fdc\u7a0b\u8ba4\u8bc1\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u67e5\u770b\u654f\u611f\u4fe1\u606f\u6216\u8fdb\u884c\u8fdb\u4e00\u6b65\u7684\u653b\u51fb\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": "Cisco Unified Communications Manager\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2020-03755\uff09\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Cisco Cisco Unified Communications Manager \u003c=10.5(2)(SU9)",
      "Cisco Cisco Unified Communications Manager \u003c=11.5(1)(SU6)",
      "Cisco Cisco Unified Communications Manager \u003c=12.0(1)(SU3)",
      "Cisco Cisco Unified Communications Manager \u003c=12.5(1)(SU1)"
    ]
  },
  "referenceLink": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20200122-cuc-info-disclosure",
  "serverity": "\u4e2d",
  "submitTime": "2020-01-23",
  "title": "Cisco Unified Communications Manager\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff08CNVD-2020-03755\uff09"
}



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.