* Fix bug with attachment handling when syncing some Cobalt findings to Jira
* Increase the amount of errors that the remote failure logging functionality is capable of reporting
* Fix bug with attachment handling when syncing some Cobalt findings to Jira
* Increase the amount of errors that the remote failure logging functionality is capable of reporting
Images that are embedded within the content of a Cobalt finding will now be embedded within the content of a Jira issue as well.
* Integration reliability improvements
* Dependency updates
* Add optional remote failure logging functionality
* Update plugin dependencies
This version adds support for switching between the EU and US versions of Cobalt, when you setup the plugin. Please select the version corresponding to your Cobalt account.
Update dependencies
This release does not have any new or altered functionality. It addresses many potential vulnerabilities by updating almost all bundled dependencies.
Added support for Jira Server versions up to 8.22.2
Per Atlassian, as of February 15, 2022, Jira customers will no longer be able to upgrade or downgrade tiers for their Server products or apps. Changing tiers will only be available by moving to either Cloud or Data Center.
The plugin remains available to our Premium and Enterprise customers.
Added some additional logging for improved troubleshooting and reporting.
Improved performance of user select in configuration for instances with more than 1000 users
Cobalt can now pass the defined Severity Level through when creating a ticket through our JIRA Server integration!
Note: A JIRA Admin must add the "Cobalt Severity" field to the necessary views within your JIRA instance.
To ensure developers have access to all the relevant information about Pentest Findings directly within JIRA, Cobalt.io now automatically adds any associated attachments from your Findings, as attachments when creating a new issue through our Bi-Directional Integration.
Internal pentest revealed an issue where a JIRA Secret Key could be used to configure multiple instances. We have patched the code and resolved this issue.
In internal pentest it was discovered that our Jira server plugin has stored XSS. Since then we have patched the code the latest version has fixed the stored XSS vulnerability.
1. Connect Cobalt and Jira server onprem platforms securely
2. Configure Cobalt for Jira setting on Cobalt
3. Auto/manual push findings from Cobalt to Jira
4. Sync ticket states from Jira to Cobalt as configured
5. Track on Cobalt movement of Jira tickets from one project to another