CNVD-2020-36737

Vulnerability from cnvd - Published: 2020-07-07
VLAI
Title
WSO2 API Manager和WSO2 API Microgateway、WSO2 IS as Key Manager代码问题漏洞
Description
WSO2 API Manager等都是美国WSO2公司的产品。WSO2 API Manager是一套API生命周期管理解决方案。WSO2 API Microgateway是一款云原生、可扩展的API网关产品。WSO2 IS as Key Manager是一款密钥管理器。 WSO2 API Manager 3.0.0及之前版本、WSO2 API Microgateway 2.2.0版本和WSO2 IS as Key Manager 5.9.0及之前版本中的Management Console存在代码问题漏洞。该漏洞源于网络系统或产品的代码开发过程中存在设计或实现不当的问题。目前没有详细的漏洞细节提供。
Severity
中
Patch Name
WSO2 API Manager和WSO2 API Microgateway、WSO2 IS as Key Manager代码问题漏洞的补丁
Patch Description
WSO2 API Manager等都是美国WSO2公司的产品。WSO2 API Manager是一套API生命周期管理解决方案。WSO2 API Microgateway是一款云原生、可扩展的API网关产品。WSO2 IS as Key Manager是一款密钥管理器。 WSO2 API Manager 3.0.0及之前版本、WSO2 API Microgateway 2.2.0版本和WSO2 IS as Key Manager 5.9.0及之前版本中的Management Console存在代码问题漏洞。该漏洞源于网络系统或产品的代码开发过程中存在设计或实现不当的问题。目前没有详细的漏洞细节提供。 目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://docs.wso2.com/display/Security/Security+Advisory+WSO2-2020-0727

Reference
https://nvd.nist.gov/vuln/detail/CVE-2020-13883
Impacted products
Name
['WSO2 API Manager <=3.0.0', 'WSO2 API Microgateway 2.2.0', 'WSO2 IS as Key Manager <=5.9.0']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-13883"
    }
  },
  "description": "WSO2 API Manager\u7b49\u90fd\u662f\u7f8e\u56fdWSO2\u516c\u53f8\u7684\u4ea7\u54c1\u3002WSO2 API Manager\u662f\u4e00\u5957API\u751f\u547d\u5468\u671f\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002WSO2 API Microgateway\u662f\u4e00\u6b3e\u4e91\u539f\u751f\u3001\u53ef\u6269\u5c55\u7684API\u7f51\u5173\u4ea7\u54c1\u3002WSO2 IS as Key Manager\u662f\u4e00\u6b3e\u5bc6\u94a5\u7ba1\u7406\u5668\u3002\n\nWSO2 API Manager 3.0.0\u53ca\u4e4b\u524d\u7248\u672c\u3001WSO2 API Microgateway 2.2.0\u7248\u672c\u548cWSO2 IS as Key Manager 5.9.0\u53ca\u4e4b\u524d\u7248\u672c\u4e2d\u7684Management Console\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u7684\u4ee3\u7801\u5f00\u53d1\u8fc7\u7a0b\u4e2d\u5b58\u5728\u8bbe\u8ba1\u6216\u5b9e\u73b0\u4e0d\u5f53\u7684\u95ee\u9898\u3002\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://docs.wso2.com/display/Security/Security+Advisory+WSO2-2020-0727",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-36737",
  "openTime": "2020-07-07",
  "patchDescription": "WSO2 API Manager\u7b49\u90fd\u662f\u7f8e\u56fdWSO2\u516c\u53f8\u7684\u4ea7\u54c1\u3002WSO2 API Manager\u662f\u4e00\u5957API\u751f\u547d\u5468\u671f\u7ba1\u7406\u89e3\u51b3\u65b9\u6848\u3002WSO2 API Microgateway\u662f\u4e00\u6b3e\u4e91\u539f\u751f\u3001\u53ef\u6269\u5c55\u7684API\u7f51\u5173\u4ea7\u54c1\u3002WSO2 IS as Key Manager\u662f\u4e00\u6b3e\u5bc6\u94a5\u7ba1\u7406\u5668\u3002\r\n\r\nWSO2 API Manager 3.0.0\u53ca\u4e4b\u524d\u7248\u672c\u3001WSO2 API Microgateway 2.2.0\u7248\u672c\u548cWSO2 IS as Key Manager 5.9.0\u53ca\u4e4b\u524d\u7248\u672c\u4e2d\u7684Management Console\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u3002\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u7f51\u7edc\u7cfb\u7edf\u6216\u4ea7\u54c1\u7684\u4ee3\u7801\u5f00\u53d1\u8fc7\u7a0b\u4e2d\u5b58\u5728\u8bbe\u8ba1\u6216\u5b9e\u73b0\u4e0d\u5f53\u7684\u95ee\u9898\u3002\u76ee\u524d\u6ca1\u6709\u8be6\u7ec6\u7684\u6f0f\u6d1e\u7ec6\u8282\u63d0\u4f9b\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": "WSO2 API Manager\u548cWSO2 API Microgateway\u3001WSO2 IS as Key Manager\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "WSO2  API Manager \u003c=3.0.0",
      "WSO2  API Microgateway 2.2.0",
      "WSO2  IS as Key Manager \u003c=5.9.0"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2020-13883",
  "serverity": "\u4e2d",
  "submitTime": "2020-06-08",
  "title": "WSO2 API Manager\u548cWSO2 API Microgateway\u3001WSO2 IS as Key Manager\u4ee3\u7801\u95ee\u9898\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.