Workaround for CVE-2019-14994

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only. This article only applies to Atlassian products on the server and data center platforms.

Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.


Affected Jira Service Management versions in CVE-2019-14994 will allow non-application access users - Service Management Customers to path traverse to see restricted issues in the Jira instance.

This allows Service Management Customers who normally don't have access to tickets that are not their own to view details of tickets contained in the XML generated results in all Jira Service Management projects.

Jira Software and Core projects will be affected if their Browse Project permission is set to Group - Anyone.

Affected versions

  • All versions before 3.9.16

  • 3.10.x

  • 3.11.x

  • 3.12.x

  • 3.13.x

  • 3.14.x

  • 3.15.x

  • 3.16.x before 3.16.8 (the fixed version for 3.16.x)

  • 4.0.x

  • 4.1.x before 4.1.3 (the fixed version for 4.1.x)

  • 4.2.x before 4.2.5 (the fixed version for 4.2.x)

  • 4.3.x before 4.3.4 (the fixed version for 4.3.x)

  • 4.4.0

Permanent resolution below along with workarounds if immediate upgrade is not possible


Upgrade to fixed version of Jira Service Management

  • 3.9.16

  • 3.16.8

  • 4.1.3

  • 4.2.5

  • 4.3.4

  • 4.4.1


Block path traversals or limit tickets from Jira Software/Core projects.

Workaround to stop Jira Software/Core project returned in the resulting XML

Set all Jira Software/Core projects' Browse Project permission to certain groups

  1. Go to Project Settings → Permissions
  2. Set Browse Project permission to groups that should only have access to their respective Jira Software/Core projects.

Workaround 1.

Redirect requests to Jira containing .. to a safe URL

  1. Add the following to the <urlrewrite> section of [jira-installation-directory]/atlassian-jira/WEB-INF/urlrewrite.xml:

        <to type="temporary-redirect">/</to>
  2. Save the urlrewrite.xml
  3. Restart Jira

Workaround 2.

Block requests to Jira containing .. at the reverse proxy or load balancer level


  1. Add the following into the .conf file that contains the virtualhost that proxies to Jira

    <LocationMatch "/(.*\.\.)">
       Order Allow,Deny
        Deny from  all

    example below -

    <VirtualHost *:80>
        ProxyRequests Off
        ProxyVia Off
        <Proxy *>
             Require all granted
        ProxyPass /jira  http://ipaddress:8080/jira
        ProxyPassReverse /jira  http://ipaddress:8080/jira
        <LocationMatch "/(.*\.\.)">
         Order Allow,Deny
         Deny from  all
  2. Restart your Apache proxy


  1. Add the following into the .conf file that contains the server block that proxies to Jira inside location block

    if ($uri ~* "/.*\.\."){   return 405;}

    example below -

        location /jira {
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_pass http://ipaddress:8080/jira;
            client_max_body_size 10M;
            if ($uri ~* "/.*\.\."){   return 405;}
  2. Restart your NGINX

ProductJira Service Management

Last modified on Jun 22, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.