The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Our maintenance/support contract ended, we're on LT 7.13
Are we able to patch to 7.13.7 without an active support license?
The plan was to migrate to the cloud service, which is why it lapsed.
Hello @Jeff McMurray ! Welcome to the Atlassian Community!
To update your version of Confluence, even to the 7.13.7 version, you'll need an active license/maintenance agreement.
You actually need to be current for your migration as well.
One solution I see is getting a trial Data Center license. Details are here: https://support.atlassian.com/migration/docs/migrate-to-cloud-with-an-expired-server-license/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, thanks, it looks like the trial and migrate will work.
Thanks for the help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wait, so does this mean that there is no fix for CVE-2022-26134 if you don't currently have support/maintenance? Our maintenance is also lapsed and we are on confluence server 7.4.3. This doesn't seem acceptable for Atlassian to leave those without maintenance exposed to a critical remote code execution vulnerability currently being exploited by threat actors. Is everyone in this boat rushing out to purchase thousands of dollars in maintenance just so they dont get hacked?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, pretty ridiculous. It seems like it should be a patch outside of maintenance contracts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What about applying the mitigation described in the advisory?
That should work regarding the license status if I'm not mistaken.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Rodolfo, We have already implemented those changes, however Atlassian lists it specifically as a TEMPORARY (in bold) workaround, which is the cause of my concern. I would feel better about it if they didn't emphasize that it should be temporary. I guess to that response, my question is... Are we safe to implement this "temporary workaround" for a few years, or does it still leave some vulnerabilities?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.