lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Jan 2017 15:50:30 -0300
From: jlss <>
Subject: [FD] Persisted Cross-Site Scripting (XSS) in Confluence Jira

=====[ Tempest Security Intelligence - ADV-3/2016 CVE-2016-6283

  Persisted Cross-Site Scripting (XSS) in Confluence Jira Software

        - Jodson Santos

  Tempest Security Intelligence - Recife, Pernambuco - Brazil

=====[ Table of Contents

1. Overview
2. Detailed description
3. Affected versions & Solutions
4. Timeline of disclosure
5. Thanks & Acknowledgements
6. References

=====[1. Overview

 * System affected  : Atlassian Confluence
 * Software Version : 5.9.12
                      Other versions or models may also be affected.
 * Impact           : This vulnerability allows an attacker to use
                      platform to deliver attacks against other users.

=====[2. Detailed description

Atlassian Confluence version 5.9.12 is vulnerable to persistent cross-site
scripting (XSS) because it fails to securely validate user controlled data,
thus making it possible for an attacker to supply crafted input in order to
harm users. The bug occurs at pages carrying attached files, even though
attached file name parameter is correctly sanitized upon submission, it is
possible for an attacker to later edit the attached file name property and
supply crafted data (i.e HTML tags and script code) without the
occurrence of
any security checks, resulting in an exploitable persistent XSS.

In order to reproduce the vulnerability, go to a page with an attached
click on "Attachments" in order to list the page's attachments, and then
on "Properties" for the file of your choice. Edit the file name to, for
example, <script>alert(1)</script>test.pdf and then save the changes.
the XSS is not executed within the page display, it is possible to
trigger the
execution of the supplied code while performing a search within
Confluence in
which results include the attachment with crafted file name. For that
the search terms " or * will promptly display the file and execute the
javascript code.

As a means to further enlighten this, the following excerpt demonstrates
request with the malicious insertion within the newFileName field:

} HTTP/1.1
Host: {confluence host}
Cookie:; JSESSIONID={redacted};
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: {redacted}


It is worth noting that the issue may affect users regardless of privilege
levels, since the malicious page/attachment can be browsed by any user
the Atlassian Confluence instance.

=====[3. Affected versions & Solutions

This test was performed against Atlassian Confluence version 5.9.12.

According to vendor's response, the vulnerability is addressed and the
fix is
part of the 5.10.6 release.

=====[4. Timeline of disclosure

Jul/07/2016 - Vendor acknowledged the vulnerability.
Aug/04/2016 - Vendor released the fix for the vulnerability in version

=====[5. Thanks & Acknowledgements

  - Tempest Security Intelligence / Tempest's Pentest Team [1]
  - Joaquim Brasil
  - Heyder Andrade
  - Breno Cunha

=====[6. References


Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists