Workaround for CVE-2019-15003

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。

*Fisheye および Crucible は除く


問題

Affected Jira Service Management versions in CVE-2019-15003 will allow non-application access users - Service Management Customers to see restricted information in the Jira instance.

This allows Service Management Customers who normally don't have access to Jira information, this authorization bypass allows remote attackers with portal access to gain direct access to Jira with the same permissions.

This affects Jira Service Management portals that have the "Anyone can email the service project or raise a request in the portal" setting enabled, exploitation allows an attacker to view all issues within all Jira projects contained in the vulnerable instance.

影響バージョン

  • All versions before 3.9.17
  • 3.10.x
  • 3.11.x
  • 3.12.x
  • 3.13.x
  • 3.14.x
  • 3.15.x
  • 3.16.x before 3.16.11 (the fixed version for 3.16.x)
  • 4.0.x
  • 4.1.x
  • 4.2.x before 4.2.6 (the fixed version for 4.2.x)
  • 4.3.x before 4.3.5 (the fixed version for 4.3.x)
  • 4.4.x before 4.4.3 (the fixed version for 4.4.x)
  • 4.5.x before 4.5.1 (the fixed version for 4.5.x)


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

ソリューション

Upgrade to fixed version of Jira Service Management

  • 3.9.17

  • 3.16.11

  • 4.2.6

  • 4.3.5

  • 4.4.3

  • 4.5.1

回避策

Block authorization bypass.

Workaround 1.

Redirect requests to Jira containing jspa, jspx, jsp to a safe URL

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

    <rule>
        <from>(?s)/servicedesk/.*\.jsp.*</from>
        <to type="temporary-redirect">/</to>
    </rule>
  2. urlrewrite.xml を保存します。
  3. Jira を再起動します。

Workaround 2.

Block requests to Jira for authorization bypass at the reverse proxy or load-balancer level

Apache

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

    <LocationMatch "/servicedesk/.*\.jsp.*">
       Order Allow,Deny
        Deny from  all
    </LocationMatch>

    example below -

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

NGINX

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

    if ($uri ~* "/servicedesk/.*\.jsp.*"){ return 403;}

    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 ~* "/servicedesk/.*\.jsp.*"){ return 403;}
     }
  2. Restart your NGINX


説明 CVE-2019-15003
製品Jira Service Management

最終更新日 2021 年 6 月 22 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.