Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25468

Request Smuggling org.apache.tomcat:tomcat-coyote Dependency in Jira Software Data Center and Server

XMLWordPrintable

    • 7.5
    • High
    • CVE-2022-42252
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
    • Patch Management
    • Jira Software Data Center, Jira Software Server

      This High severity org.apache.tomcat:tomcat-coyote Dependency vulnerability was introduced in version 9.4.0 of Jira Software Data Center and Server.

      This org.apache.tomcat:tomcat-coyote Dependency vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has no impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.

      Atlassian recommends that Jira Software 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:

      • Jira Software Data Center and Server 9.4: Upgrade to a release greater than or equal to 9.4.12

      See the release notes. You can download the latest version of Jira Software Data Center and Server from the download center.

      The National Vulnerability Database provides the following description for this vulnerability: If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

          Form Name

            [JSWSERVER-25468] Request Smuggling org.apache.tomcat:tomcat-coyote Dependency in Jira Software Data Center and Server

            Christopher Vasquez added a comment -

            @oufiniamine, it looks like Jira Server v8.20.30 came bundled with Apache Tomcat v8.5.91 (reference: https://confluence.atlassian.com/jiracore/bundled-tomcat-and-java-versions-1013854250.html).

            This looks like a "request smuggling" vulnerability, according to the description above. Relevant to you, "If Apache Tomcat 8.5.0 to 8.5.82 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header."

            Check the "rejectIllegalHeader" setting in your server.xml file. Chances are it is enabled, but checking twice and cutting once never hurts.

            Good Luck.

            Christopher Vasquez added a comment - @oufiniamine, it looks like Jira Server v8.20.30 came bundled with Apache Tomcat v8.5.91 (reference: https://confluence.atlassian.com/jiracore/bundled-tomcat-and-java-versions-1013854250.html ). This looks like a "request smuggling" vulnerability, according to the description above. Relevant to you, "If Apache Tomcat 8.5.0 to 8.5.82 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header." Check the "rejectIllegalHeader" setting in your server.xml file. Chances are it is enabled, but checking twice and cutting once never hurts. Good Luck.

            oufiniamine added a comment -

            Is Jira server 8.20.30 affected?

            oufiniamine added a comment - Is Jira server 8.20.30 affected?
            Paul Theriault made changes -
            Resolution New: Done [ 17 ]
            Status Original: Draft [ 12872 ] New: Published [ 12873 ]
            Paul Theriault made changes -
            Security Original: Atlassian Staff [ 10750 ]
            Zachary Echouafni made changes -
            Summary Original: org.apache.tomcat:tomcat-coyote Dependency in Jira Software Data Center and Server New: Request Smuggling org.apache.tomcat:tomcat-coyote Dependency in Jira Software Data Center and Server
            Guillermo Jimenez made changes -
            Description Original: This High severity Third-Party Dependency vulnerability was introduced in version 9.4.0 of Jira Software Data Center and Server.

            This Third-Party Dependency vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has no impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.

            Atlassian recommends that Jira Software 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:

            * Jira Software Data Center and Server 9.4: Upgrade to a release greater than or equal to 9.4.12



            See the release notes. You can download the latest version of Jira Software Data Center and Server from the download center.

            The National Vulnerability Database provides the following description for this vulnerability: If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

            		 New: This High severity org.apache.tomcat:tomcat-coyote Dependency vulnerability was introduced in version 9.4.0 of Jira Software Data Center and Server.

            This org.apache.tomcat:tomcat-coyote Dependency vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation which has no impact to confidentiality, high impact to integrity, no impact to availability, and requires no user interaction.

            Atlassian recommends that Jira Software 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:

            * Jira Software Data Center and Server 9.4: Upgrade to a release greater than or equal to 9.4.12



            See the release notes. You can download the latest version of Jira Software Data Center and Server from the download center.

            The National Vulnerability Database provides the following description for this vulnerability: If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

            Guillermo Jimenez made changes -
            Summary Original: Third-Party Dependency in Jira Software Data Center and Server New: org.apache.tomcat:tomcat-coyote Dependency in Jira Software Data Center and Server
            Security Metrics Bot made changes -
            Labels Original: security New: advisory advisory-to-release dont-import security
            Security Metrics Bot created issue -

              Unassigned Unassigned
              security-metrics-bot Security Metrics Bot
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: