A security vulnerability was recently identified and fixed in Elements Connect. Here are the details about the issue, its impact and the analysis and actions taken.

Nature of the issue

The vulnerability was present since the first public version of Elements Connect for Jira Cloud.
The vulnerability meant that an admin user could get a datasource configuration (except passwords) of another Jira instance as long as it was cached.
This vulnerability has been rated as medium, according to the scale published on the Common Vulnerability Scoring System (CVSS).
The vulnerability was brought to our notice by the Bug Bounty Program on  .

Impact

Based on our investigations, the vulnerability has not been exploited.

Analysis and actions taken

Once we detected the issue, a plan was then elaborated by the IT team to analyse the situation, bring a fix for the issue and deploy it as quickly as possible.
Our investigations revealed that the problem was caused by a configuration problem in our cache system.

We fixed the cache configuration in order to remove the possibility to access cached datasources of other Jira instances.

Deployment of the fixed version was conducted by following the usual CI procedure.
On top of the automatic tests, we made another series of tests to ensure that the problem was fixed in production.

Conclusion

We want you to know that we take this issue very seriously. We are conducting a thorough review of our internal processes to ensure this does not occur again for our customers.
If you have any questions, please feel free to raise a support request at support.elements-apps.com referencing "ECC-1036".