CNVD-2019-08178

Vulnerability from cnvd - Published: 2019-03-26
VLAI
Title
Atlassian Confluence Server和Atlassian Data Center服务器端请求伪造漏洞
Description
Atlassian Confluence Server和Atlassian Data Center都是澳大利亚Atlassian公司的产品。Atlassian Confluence Server是一套专业的企业知识管理与协同软件,也可以用于构建企业WiKi。Atlassian Data Center是一套数据中心系统。 Atlassian Confluence Server和Atlassian Data Center 6.6.7之前版本、6.7.0版本至6.8.5之前版本和6.9.0版本至6.9.3之前版本中的WebDAV端点存在服务器端请求伪造漏洞。远程攻击者可利用该漏洞凭借Confluence Server或Data Center实例发送任意HTTP和WebDAV请求。
Severity
中
Patch Name
Atlassian Confluence Server和Atlassian Data Center服务器端请求伪造漏洞的补丁
Patch Description
Atlassian Confluence Server和Atlassian Data Center都是澳大利亚Atlassian公司的产品。Atlassian Confluence Server是一套专业的企业知识管理与协同软件,也可以用于构建企业WiKi。Atlassian Data Center是一套数据中心系统。 Atlassian Confluence Server和Atlassian Data Center 6.6.7之前版本、6.7.0版本至6.8.5之前版本和6.9.0版本至6.9.3之前版本中的WebDAV端点存在服务器端请求伪造漏洞。远程攻击者可利用该漏洞凭借Confluence Server或Data Center实例发送任意HTTP和WebDAV请求。目前,供应商发布了安全公告及相关补丁信息,修复了此漏洞。
Formal description

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

Reference
https://jira.atlassian.com/browse/CONFSERVER-57971 http://seclists.org/bugtraq/2019/Mar/40
Impacted products
Name
['Atlassian Confluence Server <6.6.7', 'Atlassian Confluence Server >=6.7.0,<=6.8.5', 'Atlassian Confluence Server >=6.9.0,<=6.9.3', 'Atlassian Data Center <6.6.7', 'Atlassian Data Center >=6.7.0,<=6.8.5', 'Atlassian Data Center >=6.9.0,<=6.9.3']
Show details on source website

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2019-3395"
    }
  },
  "description": "Atlassian Confluence Server\u548cAtlassian Data Center\u90fd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4ea7\u54c1\u3002Atlassian Confluence Server\u662f\u4e00\u5957\u4e13\u4e1a\u7684\u4f01\u4e1a\u77e5\u8bc6\u7ba1\u7406\u4e0e\u534f\u540c\u8f6f\u4ef6\uff0c\u4e5f\u53ef\u4ee5\u7528\u4e8e\u6784\u5efa\u4f01\u4e1aWiKi\u3002Atlassian Data Center\u662f\u4e00\u5957\u6570\u636e\u4e2d\u5fc3\u7cfb\u7edf\u3002\n\nAtlassian Confluence Server\u548cAtlassian Data Center 6.6.7\u4e4b\u524d\u7248\u672c\u30016.7.0\u7248\u672c\u81f36.8.5\u4e4b\u524d\u7248\u672c\u548c6.9.0\u7248\u672c\u81f36.9.3\u4e4b\u524d\u7248\u672c\u4e2d\u7684WebDAV\u7aef\u70b9\u5b58\u5728\u670d\u52a1\u5668\u7aef\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u51ed\u501fConfluence Server\u6216Data Center\u5b9e\u4f8b\u53d1\u9001\u4efb\u610fHTTP\u548cWebDAV\u8bf7\u6c42\u3002",
  "discovererName": "unknwon",
  "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/CONFSERVER-57971",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2019-08178",
  "openTime": "2019-03-26",
  "patchDescription": "Atlassian Confluence Server\u548cAtlassian Data Center\u90fd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4ea7\u54c1\u3002Atlassian Confluence Server\u662f\u4e00\u5957\u4e13\u4e1a\u7684\u4f01\u4e1a\u77e5\u8bc6\u7ba1\u7406\u4e0e\u534f\u540c\u8f6f\u4ef6\uff0c\u4e5f\u53ef\u4ee5\u7528\u4e8e\u6784\u5efa\u4f01\u4e1aWiKi\u3002Atlassian Data Center\u662f\u4e00\u5957\u6570\u636e\u4e2d\u5fc3\u7cfb\u7edf\u3002\r\n\r\nAtlassian Confluence Server\u548cAtlassian Data Center 6.6.7\u4e4b\u524d\u7248\u672c\u30016.7.0\u7248\u672c\u81f36.8.5\u4e4b\u524d\u7248\u672c\u548c6.9.0\u7248\u672c\u81f36.9.3\u4e4b\u524d\u7248\u672c\u4e2d\u7684WebDAV\u7aef\u70b9\u5b58\u5728\u670d\u52a1\u5668\u7aef\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u3002\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u51ed\u501fConfluence Server\u6216Data Center\u5b9e\u4f8b\u53d1\u9001\u4efb\u610fHTTP\u548cWebDAV\u8bf7\u6c42\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 Confluence Server\u548cAtlassian Data Center\u670d\u52a1\u5668\u7aef\u8bf7\u6c42\u4f2a\u9020\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Atlassian Confluence Server \u003c6.6.7",
      "Atlassian Confluence Server \u003e=6.7.0\uff0c\u003c=6.8.5",
      "Atlassian Confluence Server \u003e=6.9.0\uff0c\u003c=6.9.3",
      "Atlassian Data Center \u003c6.6.7",
      "Atlassian Data Center \u003e=6.7.0\uff0c\u003c=6.8.5",
      "Atlassian Data Center \u003e=6.9.0\uff0c\u003c=6.9.3"
    ]
  },
  "referenceLink": "https://jira.atlassian.com/browse/CONFSERVER-57971\r\nhttp://seclists.org/bugtraq/2019/Mar/40",
  "serverity": "\u4e2d",
  "submitTime": "2019-03-26",
  "title": "Atlassian Confluence Server\u548cAtlassian Data Center\u670d\u52a1\u5668\u7aef\u8bf7\u6c42\u4f2a\u9020\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.