You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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/
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?
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?