Does this workaround also applies to LTS 7.13.5 although only version >7.15 are mentioned?
If you are unable to upgrade Confluence immediately, then as a temporary workaround, you can mitigate the CVE-2022-26134 issue by updating the following files for the specific version of the product.
If you run Confluence in a cluster, you will need to repeat this process on each node. You don't need to shut down the whole cluster to apply this mitigation.
Shut down Confluence.
Download the following 1 file to the Confluence server:
Delete (or move the following JAR outside of the Confluence install directory):
<confluence-install>/confluence/WEB-INF/lib/xwork-1.0.3-atlassian-8.jar
Do not leave a copy of this old JAR in the directory.
Copy the downloaded xwork-1.0.3-atlassian-10.jar into <confluence-install>/confluence/WEB-INF/lib/
Check the permissions and ownership on the new xwork-1.0.3-atlassian-10.jar file matches the existing files in the same directory.
Start Confluence.
There are different workarounds steps depending on your version. Those are the steps for 7.15 and higher versions. But the advisory also contains a different workaround steps for 7.0.0 - 7.14.x versions. Search for the phrase
and you will find slightly different mitigation steps for those versions.
Hi @Andy Heinzer we are using Confluence Server v. 7.4.11.
I have followed mitigation steps under "For Confluence 7.0.0 - Confluence 7.14.2".
After copying these files in respective directories, confluence app is not loading. Getting some errors in Catalina.out and atlassian-confluence.log.
Shall I open another case for it ? or could you help me?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Venkata Mangipudi Please create a technical support request by visiting https://support.atlassian.com/contact/ I recommend that you have a billing or technical contact of your Confluence server license open a support case. Otherwise users that are not listed within the SEN could be redirected back here to Community.
For startup problems like you have mentioned, it is important for our support teams to be able to gather those logs to help here.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.