Browser script execution via crafted fieldID
Published Jun 7, 2021 · Updated Oct 17, 2024
Cross-site scripting in CardLayoutConfigTable in Atlassian Jira Server and Jira Data Center allows remote attackers to inject script via fieldID. Atlassian identifies fieldID as the vulnerable input but has not published a patch diff or further details about the missing output neutralization. A victim must render the attacker-controlled field value in a browser, allowing arbitrary HTML or JavaScript to run in the Jira origin.
Summary
What happened
Cross-site scripting in CardLayoutConfigTable in Atlassian Jira Server and Jira Data Center allows remote attackers to inject script via fieldID. Atlassian identifies fieldID as the vulnerable input but has not published a patch diff or further details about the missing output neutralization. A victim must render the attacker-controlled field value in a browser, allowing arbitrary HTML or JavaScript to run in the Jira origin.
The record
- CVE
- CVE-2021-26079
- Published
- Jun 7, 2021
- Updated
- Oct 17, 2024
- Vendor
- Atlassian
- Product
- Jira Server
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 7, 2021CVE publishedPublication date reported by the CVE source.
- Oct 17, 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=8.14.0 <unspecified
- Affected versionversion=8.6.0 <unspecified
- Affected versionversion=unspecified <8.13.7
- Affected versionversion=unspecified <8.17.0
- Affected versionversion=unspecified <8.5.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