I'm running Bitbucket Server 6.7.1 and I saw three bug fixes for 6.7.3 relating to Remote Code Execution errors on the Bitbucket 6.7 release notes page. I believe it had to do with the in-code editor.
They linked to these issues (which now display that the issue does not exist)
https://jira.atlassian.com/browse/BSERV-12100?src=confmacro&_ga=2.102605825.1402435397.1578323223-396634458.1525373069
https://jira.atlassian.com/browse/BSERV-12099?src=confmacro&_ga=2.102605825.1402435397.1578323223-396634458.1525373069
https://jira.atlassian.com/browse/BSERV-12098?src=confmacro&_ga=2.102605825.1402435397.1578323223-396634458.1525373069
What happened to the issues? Is 6.7.1 a safe version to run or do I need to upgrade to 6.7.3 anyway?
Hey there,
We published a security advisory just a few minutes ago which applies to your current Bitbucket Server version (6.7.1). As these vulnerabilities are listed as critical, the related issues on jira.atlasian.com were set to private until we publicly announced the advisory. Sorry for the confusion briefly while these issues made it into the release notes but you weren't able to access the details.
The public advisory is available here: https://confluence.atlassian.com/bitbucketserver/bitbucket-server-security-advisory-2020-01-15-985498238.html
Emails have been sent to technical contacts for accounts with Bitbucket licenses. If you didn't get an email yet but feel like you should have, you can check your communication preferences at my.atlassian.com/email, then look at the "Tech Alerts" section to see which products you're subscribed to alerts for.
Given that only 1 of the 3 vulnerabilities in the advisory has a workaround, I would suggest upgrading to 6.7.3 anyway.
Cheers,
Daniel | Atlassian Support
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.