{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-39115 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-39115 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-39115 is a high-severity code injection vulnerability in Atlassian Jira Service Desk Data Center, published on 1 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-39115 and fix it if it is affected.\n\nWhat it is: CVE-2021-39115 is a high-severity code injection vulnerability in Atlassian Jira Service Desk Data Center, published on 1 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-39115 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Service Desk Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-39115/ (Markdown: https://insights.sbomify.com/CVE-2021-39115/index.md)","id":"CVE-2021-39115","markdown":"https://insights.sbomify.com/CVE-2021-39115/index.md","name":"CVE-2021-39115","record":{"aliases":["GHSA-82p4-m5cc-j7c9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Service Management","requires_auth":"high_privilege","summary":"Remote attackers with administrator access can execute arbitrary code or commands via Server-Side Template Injection in email templates.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_service_desk","vendor":"atlassian"},{"product":"jira_service_management","vendor":"atlassian"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-96","name":"Improper Neutralization of Directives in Statically Saved Code"}],"description":"Affected versions of Atlassian Jira Service Management Server and Data Center allow remote attackers with \"Jira Administrators\" access to execute arbitrary Java code or run arbitrary system commands via a Server_Side Template Injection vulnerability in the Email Template feature. The affected versions are before version 4.13.9, and from version 4.14.0 before 4.18.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-09-07","github_poc":1,"max_poc_stars":48,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-09-07T09:03:35Z","kind":"github_poc","ref":"https://github.com/PetrusViet/CVE-2021-39115","stars":48,"title":"Template Injection in Email Templates leads to code execution on Jira Service Management Server"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in Jira Service Desk Data Center","id":"CVE-2021-39115","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Jira Data Center","id":"CVE-2021-39116"},"packages":[],"prev":{"headline":"Code injection in Confluence Data Center","id":"CVE-2021-39114"},"products":["Jira Service Desk Data Center","Jira Service Desk Server"],"published":"2021-09-01","related":[{"cvss_score":7.5,"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-15004","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":7.5,"headline":"Path traversal in Jira Service Desk Data Center","id":"CVE-2019-14994","kev_date_added":null,"published":"2019-09-19"},{"cvss_score":5.7,"headline":"Server-side request forgery in Jira Service Management Data Center","id":"CVE-2021-43959","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":5.3,"headline":"Missing authorization in Jira Service Desk Data Center","id":"CVE-2019-15003","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":4.8,"headline":"Cross-site scripting in Jira Service Desk Server and Data Center","id":"CVE-2020-14166","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":4.3,"headline":"Information disclosure in Jira Service Desk Server","id":"CVE-2020-14180","kev_date_added":null,"published":"2020-09-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-11","vendors":["Atlassian"]},"summary":"Remote attackers with administrator access can execute arbitrary code or commands via Server-Side Template Injection in email templates.","url":"https://insights.sbomify.com/CVE-2021-39115/"}