Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Risk of cross-site scripting attacks w/Stylesheet enabled, what about Aptivista CSS macro?

So the following Confluence doc mentions the XSS risk, does the Adaptavista CSS Stylesheet macro pose the same security risk?

https://confluence.atlassian.com/doc/styling-confluence-with-css-166528400.html

https://www.adaptavist.com/doco/display/CFP/Style+Sheet

 

1 answer

1 accepted

0 votes
Answer accepted

Hello John.

Thank you for contacting us about this!

According to Content Formatting documentation from Adaptavist:

As Confluence is a content-management system that allows user-generated content to be posted on the web, precautions have been taken within the Content Formatting Add-On to prevent cross-site scripting attacks:

The Content Formatting html macros specifically prevent the use of unknown HTML attributes, and all parameter values are checked against an allowable range to ensure that they are not being abused.

For example, where an html attribute has an 'enum' set of values, ONLY those values are allowed; where it's a free text attribute, the value is checked for breaking out of the attribute rules. If any 'bad' values are found a macro exception is thrown and the output is not rendered.

Additional Precautions:

  • All of the 'form' html elements are disabled by default and must be manually enabled by an administrator.
  • JavaScript attributes are not allowed and cannot be enabled e.g. 'onclick'.

I hope that clarifies things for you, but I've included your question in the Adaptavist collection as well, in case anyone from Adaptavist has any further information for you regarding this.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

81 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you