CVE DatabaseCVE-2019-11581
한국어 권고문 →
CVE-2019-115819.8/CRITICALCISA KEVCWE-74CWE-74

Atlassian Jira Server and Data Center Remote Code Execution (RCE) Vulnerability (CVE-2019-11581) Security Advisory

⚡ Jump to Patch
Affected Vendors
atlassian
Affected Components
jira_server, jira_data_center
Published Date
2019-08-09
CVSS v3.1
9.8
CRITICAL
EPSS (30d)
84.6%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Jira Server and Data Center versions from 4.4.0 before 7.6.14, 7.7.0 before 7.13.5, 8.0.0 before 8.0.3, 8.1.0 before 8.1.2, and 8.2.0 before 8.2.3

Impact

Unauthenticated remote attackers can exploit the email template rendering logic to execute arbitrary system commands, leading to full system compromise

Mitigation

Immediately upgrade Jira Server and Data Center to the patched versions (7.6.14, 7.13.5, 8.0.3, 8.1.2, 8.2.3 or later)

Affected Products & Version Scope

Jira Server and Data Center: 4.4.0 to < 7.6.14, 7.7.0 to < 7.13.5, 8.0.0 to < 8.0.3, 8.1.0 to < 8.1.2, and 8.2.0 to < 8.2.3

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

The primary remediation is upgrading Jira to a secure, patched release. Below are the commands to back up your current installation and prepare for the upgrade on a Linux environment.

bash
# 1. Back up Jira Home and Installation directories
tar -czvf jira_home_backup.tar.gz /var/atlassian/application-data/jira
tar -czvf jira_install_backup.tar.gz /opt/atlassian/jira

# 2. Download the secure Jira Software installer (e.g., LTS version 8.20.10)
wget https://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-software-8.20.10-x64.bin
chmod +x atlassian-jira-software-8.20.10-x64.bin

# 3. Execute the installer to perform the upgrade
sudo ./atlassian-jira-software-8.20.10-x64.bin

2. Temporary Workaround & Hardening Configuration

If an immediate upgrade is not feasible, block external access to the vulnerable endpoints using a reverse proxy or web application firewall (WAF).

nginx
# Nginx configuration block to block access to vulnerable Jira endpoints
server {
    listen 80;
    server_name jira.company.local;

    # Block ContactAdministrators action
    location ~* /Secure/ContactAdministrators {
        deny all;
        return 403;
    }

    # Block SendBulkMail action
    location ~* /Secure/SendBulkMail {
        deny all;
        return 403;
    }

    location / {
        proxy_pass http://127.0.0.1:8080;
    }
}

3. Log Audit & IoC Verification Commands

Inspect Jira access logs to identify potential exploitation attempts targeting the vulnerable endpoints and containing Velocity template payloads.

bash
# Search access logs for requests to the vulnerable endpoints
grep -Ei 'ContactAdministrators|SendBulkMail' /opt/atlassian/jira/logs/atlassian-jira-http-access*.log

# Search for common SSTI payload patterns and Java runtime execution attempts in the logs
grep -Ei '\$i18n|class\.forName|java\.lang\.Runtime' /opt/atlassian/jira/logs/atlassian-jira-http-access*.log
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
Cloudflare Enterprise & Pro WAF
Due to active exploitation in the wild (CISA KEV), immediately upgrade your Jira instances to a patched version.

Block Exploits Instantly with Managed Virtual Patching Rules

Can't patch production immediately? Deploy managed WAF rules at the edge to intercept RCE, SQLi, and deserialization payloads before they hit your origin server.

3-min setup · Automated Zero-Day Managed Rules
Practice Exploiting & Patching This Web Vulnerability in an Interactive Lab
Launch Hands-On Security Lab

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability is a Server-Side Template Injection (SSTI) vulnerability in Atlassian Jira Server and Data Center, specifically within the 'ContactAdministrators' and 'SendBulkMail' actions. The root cause lies in the improper validation of user-supplied input before passing it to the Velocity template engine. When rendering email templates, Jira dynamically evaluates input parameters without proper sandboxing, allowing template directives to be executed.

2. Exploitation Mechanics & Attack Scenario

An unauthenticated attacker can exploit this vulnerability if the 'Contact Administrators' form or bulk mailing features are enabled. By sending a crafted HTTP POST request containing malicious Velocity template syntax (e.g., leveraging $i18n.getClass().forName(...) to access Java runtime classes) to the vulnerable endpoints, the attacker forces the Velocity engine to compile and execute the payload. This results in arbitrary OS command execution under the context of the Jira service user account.

3. Infrastructure & Business Impact

With a CVSS score of 9.8 (Critical) and its inclusion in CISA's Known Exploited Vulnerabilities (KEV) catalog, this vulnerability poses an extreme risk to enterprise infrastructure. Successful exploitation allows complete takeover of the Jira application server, enabling attackers to exfiltrate proprietary source code, sensitive issue tracking data, and user credentials, or use the compromised server as a pivot point for lateral movement within the internal network.

Official Vendor Advisories & References

NVD Original English Description

There was a server-side template injection vulnerability in Jira Server and Data Center, in the ContactAdministrators and the SendBulkMail actions. An attacker is able to remotely execute code on systems that run a vulnerable version of Jira Server or Data Center. All versions of Jira Server and Data Center from 4.4.0 before 7.6.14, from 7.7.0 before 7.13.5, from 8.0.0 before 8.0.3, from 8.1.0 before 8.1.2, and from 8.2.0 before 8.2.3 are affected by this vulnerability.

Frequently Asked SecOps Questions (CVE-2019-11581)

FAQ

Q1. How critical is CVE-2019-11581 and is it actively exploited in the wild?

CVE-2019-11581 is rated CVSS 9.8 (CRITICAL) with a 30-day EPSS exploitation probability of 84.6%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2019-11581?

Primary impacted vendors include atlassian across jira_server, jira_data_center. Scope summary: Jira Server and Data Center: 4.4.0 to < 7.6.14, 7.7.0 to < 7.13.5, 8.0.0 to < 8.0.3, 8.1.0 to < 8.1.2, and 8.2.0 to < 8.2.3

Q3. What temporary mitigations or workarounds exist for CVE-2019-11581 before patching?

[Mitigation] Immediately upgrade Jira Server and Data Center to the patched versions (7.6.14, 7.13.5, 8.0.3, 8.1.2, 8.2.3 or later) Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2019-11581

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (atlassian)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2019-11581 Atlassian Jira Server and Data Center Remote Code Execution (RCE) Vulnerability (CVE-2019-11581) Security Advisory (CVSS 9.8) - Patch & Workaround | CVE Pulse