-
Public Security Vulnerability
-
Resolution: Fixed
-
Highest
-
6.10.0, 7.19.0, 7.20.0, 8.0.0, 8.1.0, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 8.8.0, 8.7.1, 8.9.0, 9.1.0, 9.0.1, 9.2.0
-
None
-
9.8
-
Critical
-
CVE-2024-50379
-
Atlassian (Internal)
-
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
-
RCE (Remote Code Execution)
-
Confluence Data Center, Confluence Server
This Critical severity org.apache.tomcat:tomcat-catalina Dependency vulnerability was introduced in version 6.10 of Confluence Data Center and Server.
This org.apache.tomcat:tomcat-catalina Dependency vulnerability, with a CVSS Score of 9.8 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires no user interaction.
Atlassian recommends that Confluence Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
- Confluence Data Center and Server 8.5: Upgrade to a release greater than or equal to 8.5.19
- Confluence Data Center and Server 9.2: Upgrade to a release greater than or equal to 9.2.1
See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html). You can download the latest version of Confluence Data Center and Server from the download center (https://www.atlassian.com/software/confluence/download-archives).
The National Vulnerability Database provides the following description for this vulnerability: Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability during JSP compilation in Apache Tomcat permits an RCE on case insensitive file systems when the default servlet is enabled for write (non-default configuration).
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.1, from 10.1.0-M1 through 10.1.33, from 9.0.0.M1 through 9.0.97.
Users are recommended to upgrade to version 11.0.2, 10.1.34 or 9.0.98, which fixes the issue.
[CONFSERVER-99215] RCE (Remote Code Execution) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center and Server
Hi. According to what we have read, this bug may not affect Linux. Is this true?
Hi,
I have an other question.
You declared this Vulnerability as critical. Wasnt it the case that Atlassian Partners got a notification for critical Vulnerabilities before the Security Bulletin is published?
I mean it would have been nice to be informed before you publish a theoretical RCE with a Score of 9.8.
Did this change?
Best Regards
Thx that also means we're not vulnerable to the other Confluence RCE tomcat vulnerability which also requires the readonly parameter to be set to false. The Redhat support site linked below also mentions this.
CONFSERVER-99216 RCE (Remote Code Execution) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center and Server - Create and track feature requests for Atlassian products.
CVE-2024-56337 - Red Hat Customer Portal
6626e80b505b : correct from my understanding Confluence isn't vulnerable for CVE-2024-50379
grep -C 10 "DefaultServlet" web.xml ... <servlet> <servlet-name>default</servlet-name> <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class> <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> <init-param> <param-name>listings</param-name> <param-value>false</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet>
To be vulnerable readonly needs to be set to false:
<init-param>
<param-name>readonly</param-name>
<param-value>false</param-value>
</init-param>
see https://medium.com/@patelvidhi4288/deep-dive-poc-of-cve-2024-50379-exploit-tomcat-vulnerability-9-8-severity-776cfcfcf3ed for background information
Interesting, thanks 957e7f42e58c. Also interesting that this is only rated at 8.1 over at Red Hat.
Question: I don't see the readonly set to false in the web.xml of our confluence server. So that would mean that the default value for readonly is still true and we wouldnt be vulnerable to this exploit. Am I correct in this assumption?
Hi 0b0d780a7617,
according to the security advisories from Red Hat (https://access.redhat.com/security/cve/CVE-2024-50379, https://access.redhat.com/security/cve/cve-2024-56337)
this should be the case if e.g. running on ext4 with default kernel config.
This flaw can only be exploited when the readonly initialization parameter value is set to false, when running on case insensitive file systems and when the application is under load, specifically when read and upload operations are performed on the same file simultaneously.
Any feedback/opinion is appreciated.
regards,
Frank
Can you please update the fix version and include 9.2.2 as well?