Is the Issue Collector a (security) risk Edited


we have a public JIRA instance that is used by our customers to report bugs directly. Now we want to implement a feedback function in our windows-software and want to use the issue-collector feature to do so.

By analyzing the issue collector functionality, we've noticed that there is no captcha, login, obviouscation or other feature that prevents users from "spamming" the public available interface to create plenty of entries in JIRA.

One you have the URL (by sniffing or using a proxy) you can simple "denial of service" JIRA by creating thousands or more JIRA tickets through the public interface.


Is there anything we're missing that Atlassian has done to prevent that kind of attack?

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published yesterday in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

260 views 5 14
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot