Authenticated code execution via template injection
Published Feb 18, 2021 · Updated Sep 16, 2024
Template injection in Atlassian Jira Server for Slack 0.0.3 through 2.0.14 allows remote authenticated users to execute arbitrary code. The affected plugin endpoint evaluates attacker-supplied template content instead of treating it as data, but Atlassian has not disclosed the endpoint, template engine, or code locus. Exploitation requires any authenticated Jira account and the non-default plugin on Jira Server or Data Center; Jira Cloud is unaffected.
Summary
What happened
Template injection in Atlassian Jira Server for Slack 0.0.3 through 2.0.14 allows remote authenticated users to execute arbitrary code. The affected plugin endpoint evaluates attacker-supplied template content instead of treating it as data, but Atlassian has not disclosed the endpoint, template engine, or code locus. Exploitation requires any authenticated Jira account and the non-default plugin on Jira Server or Data Center; Jira Cloud is unaffected.
The record
- CVE
- CVE-2021-26068
- Published
- Feb 18, 2021
- Updated
- Sep 16, 2024
- Vendor
- Atlassian
- Product
- Jira Server for Slack
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.3 <unspecified
- Affected versionversion=unspecified <2.0.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo