Confluence Community Security Advisory 2006-01-19
Confluence Security Overview and Advisories
- Confluence Community Security Advisory 2006-01-19
- Confluence Security Advisory 2005-02-09
- Confluence Security Advisory 2005-12-05
- Confluence Security Advisory 2006-01-20
- Confluence Security Advisory 2006-01-23
- Confluence Security Advisory 2006-06-14
- Confluence Security Advisory 2007-07-26
- Confluence Security Advisory 2007-08-08
- Confluence Security Advisory 2007-11-19
- Confluence Security Advisory 2007-11-27
- Confluence Security Advisory 2007-12-14
- Confluence Security Advisory 2008-01-24
- Confluence Security Advisory 2008-03-06
- Confluence Security Advisory 2008-03-19
- Confluence Security Advisory 2008-05-21
- Confluence Security Advisory 2008-07-03
- Confluence Security Advisory 2008-09-08
- Confluence Security Advisory 2008-10-14
- Confluence Security Advisory 2008-12-03
- Confluence Security Advisory 2009-01-07
- Confluence Security Advisory 2009-02-18
- Confluence Security Advisory 2009-04-15
- Confluence Security Advisory 2009-06-01
- Confluence Security Advisory 2009-06-16
- Confluence Security Advisory 2009-08-20
- Confluence Security Advisory 2009-10-06
- Confluence Security Advisory 2009-12-08
- Confluence Security Advisory 2010-05-04
- Confluence Security Advisory 2010-06-02
- Confluence Security Advisory 2010-07-06
- Confluence Security Advisory 2010-08-17
- Confluence Security Advisory 2010-09-21
- Confluence Security Advisory 2010-10-12
- Confluence Security Advisory 2010-11-15
- Confluence Security Advisory 2011-01-18
- Confluence Security Advisory 2011-03-24
- Confluence Security Advisory 2011-05-31
- Confluence Security Advisory 2012-05-17
- Confluence Security Advisory 2012-09-04
- Confluence Security Advisory 2012-09-11
- Confluence Security Advisory 2013-08-05
- Confluence Security Advisory 2014-02-26
- Confluence Security Advisory 2014-05-21
- Confluence Security Advisory - 2015-01-21
- Confluence Security Advisory - 2016-09-21
- Confluence Security Advisory - 2017-04-19
- Confluence Security Advisory - 2019-03-20
- Confluence Security Advisory - 2019-04-17
- Confluence Security Advisory - 2019-08-28
- Confluence Security Advisory - 2019-12-18
- Confluence Security Advisory - 2021-08-25
- Multiple Products Security Advisory - Unrendered unicode bidirectional override characters - CVE-2021-42574 - 2021-11-01
- Multiple Products Security Advisory - Hazelcast Vulnerable To Remote Code Execution - CVE-2016-10750
- Confluence Security Advisory 2022-06-02
- Questions For Confluence Security Advisory 2022-07-20
On this page
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
This security advisory is not endorsed by Atlassian - this is a public service advisory from a member of the confluence community. Please remember to backup any modified files, and use these instructions at your own risk. While this information is based on Confluence v2.1.2, it may have uses with older affected versions of Confluence.
The official security advisory is located at Confluence Security Advisory 2006-01-20
Problem
There is a possibility of XSS exploitation of the Full Name user profile field when displayed.
Solution
The problem was unescaped outputting of the fullname - wrapping the output in $generalUtil.htmlEncode() resolve it. The vast majority of the problem can be resolved by changing /confluence/template/includes/macros.vm
in the distribution on the following lines:
- 180
- 186
- 200
- 340
- 893
I have attached the modified macros.vm file here which you can copy into your distribution.
Scope
There are other places which are still affected which Atlassian have been made aware of, a complete resolution should be provided by Atlassian in their own offical advisory.
I hope this helps some of you!
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications