CNVD-2020-50503

Vulnerability from cnvd - Published: 2020-09-03
VLAI
Title
Atlassian JIRA Server和Atlassian JIRA Data Center跨站脚本漏洞
Description
Atlassian JIRA Server和Atlassian JIRA Data Center都是澳大利亚Atlassian公司的产品。Atlassian JIRA Server是一套缺陷跟踪管理系统的服务器版本。该系统主要用于对工作中各类问题、缺陷进行跟踪管理。Atlassian JIRA Data Center是Atlassian JIRA的数据中心版本。 Atlassian JIRA Server和Data Center 8.5.4之前版本、8.6.0及之后版本(8.6.2版本已修复)和8.7.0版本及之后版本(8.7.1版本已修复)中的文件上传功能存在跨站脚本漏洞。远程攻击者可利用该漏洞注入任意HTML或JavaScript代码。
Severity
低
Patch Name
Atlassian JIRA Server和Atlassian JIRA Data Center跨站脚本漏洞的补丁
Patch Description
Atlassian JIRA Server和Atlassian JIRA Data Center都是澳大利亚Atlassian公司的产品。Atlassian JIRA Server是一套缺陷跟踪管理系统的服务器版本。该系统主要用于对工作中各类问题、缺陷进行跟踪管理。Atlassian JIRA Data Center是Atlassian JIRA的数据中心版本。 Atlassian JIRA Server和Data Center 8.5.4之前版本、8.6.0及之后版本(8.6.2版本已修复)和8.7.0版本及之后版本(8.7.1版本已修复)中的文件上传功能存在跨站脚本漏洞。远程攻击者可利用该漏洞注入任意HTML或JavaScript代码。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

目前厂商已发布升级补丁以修复漏洞,补丁获取链接: https://jira.atlassian.com/browse/JRASERVER-70814

Reference
https://nvd.nist.gov/vuln/detail/CVE-2020-14173
Impacted products
Name
['Atlassian JIRA Server <8.5.4', 'Atlassian Jira Data Center <8.5.4', 'Atlassian JIRA Server >=8.6.0,<8.6.2', 'Atlassian Jira Data Center >=8.6.0,<8.6.2', 'Atlassian JIRA Server >=8.7.0,<8.7.1', 'Atlassian Jira Data Center >=8.7.0,<8.7.1']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2020-14173"
    }
  },
  "description": "Atlassian JIRA Server\u548cAtlassian JIRA Data Center\u90fd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4ea7\u54c1\u3002Atlassian JIRA Server\u662f\u4e00\u5957\u7f3a\u9677\u8ddf\u8e2a\u7ba1\u7406\u7cfb\u7edf\u7684\u670d\u52a1\u5668\u7248\u672c\u3002\u8be5\u7cfb\u7edf\u4e3b\u8981\u7528\u4e8e\u5bf9\u5de5\u4f5c\u4e2d\u5404\u7c7b\u95ee\u9898\u3001\u7f3a\u9677\u8fdb\u884c\u8ddf\u8e2a\u7ba1\u7406\u3002Atlassian JIRA Data Center\u662fAtlassian JIRA\u7684\u6570\u636e\u4e2d\u5fc3\u7248\u672c\u3002\n\nAtlassian JIRA Server\u548cData Center 8.5.4\u4e4b\u524d\u7248\u672c\u30018.6.0\u53ca\u4e4b\u540e\u7248\u672c\uff088.6.2\u7248\u672c\u5df2\u4fee\u590d\uff09\u548c8.7.0\u7248\u672c\u53ca\u4e4b\u540e\u7248\u672c\uff088.7.1\u7248\u672c\u5df2\u4fee\u590d\uff09\u4e2d\u7684\u6587\u4ef6\u4e0a\u4f20\u529f\u80fd\u5b58\u5728\u8de8\u7ad9\u811a\u672c\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u4efb\u610fHTML\u6216JavaScript\u4ee3\u7801\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://jira.atlassian.com/browse/JRASERVER-70814",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2020-50503",
  "openTime": "2020-09-03",
  "patchDescription": "Atlassian JIRA Server\u548cAtlassian JIRA Data Center\u90fd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4ea7\u54c1\u3002Atlassian JIRA Server\u662f\u4e00\u5957\u7f3a\u9677\u8ddf\u8e2a\u7ba1\u7406\u7cfb\u7edf\u7684\u670d\u52a1\u5668\u7248\u672c\u3002\u8be5\u7cfb\u7edf\u4e3b\u8981\u7528\u4e8e\u5bf9\u5de5\u4f5c\u4e2d\u5404\u7c7b\u95ee\u9898\u3001\u7f3a\u9677\u8fdb\u884c\u8ddf\u8e2a\u7ba1\u7406\u3002Atlassian JIRA Data Center\u662fAtlassian JIRA\u7684\u6570\u636e\u4e2d\u5fc3\u7248\u672c\u3002\r\n\r\nAtlassian JIRA Server\u548cData Center 8.5.4\u4e4b\u524d\u7248\u672c\u30018.6.0\u53ca\u4e4b\u540e\u7248\u672c\uff088.6.2\u7248\u672c\u5df2\u4fee\u590d\uff09\u548c8.7.0\u7248\u672c\u53ca\u4e4b\u540e\u7248\u672c\uff088.7.1\u7248\u672c\u5df2\u4fee\u590d\uff09\u4e2d\u7684\u6587\u4ef6\u4e0a\u4f20\u529f\u80fd\u5b58\u5728\u8de8\u7ad9\u811a\u672c\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u6ce8\u5165\u4efb\u610fHTML\u6216JavaScript\u4ee3\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": "Atlassian JIRA Server\u548cAtlassian JIRA Data Center\u8de8\u7ad9\u811a\u672c\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Atlassian JIRA Server \u003c8.5.4",
      "Atlassian Jira Data Center \u003c8.5.4",
      "Atlassian JIRA Server \u003e=8.6.0\uff0c\u003c8.6.2",
      "Atlassian Jira Data Center \u003e=8.6.0\uff0c\u003c8.6.2",
      "Atlassian JIRA Server \u003e=8.7.0\uff0c\u003c8.7.1",
      "Atlassian Jira Data Center \u003e=8.7.0\uff0c\u003c8.7.1"
    ]
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2020-14173",
  "serverity": "\u4f4e",
  "submitTime": "2020-07-03",
  "title": "Atlassian JIRA Server\u548cAtlassian JIRA Data Center\u8de8\u7ad9\u811a\u672c\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.