Jira Software 8.17
Jira Software 8.17
The Jira Software 8.17 reached end of service life on May 18, 2023 — Jira Software no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Jira Software 8.17 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- jira-software
- release
- 8.17
- product Label
- Jira Software
- release Label
- 8.17
- codename
- lts
- latest Version
- 8.17.1
- release Date
- 2021-05-17
- maintained
- source Url
- https://endoflife.date/jira-software
Lifecycle Dates
- End of Service Life
- May 18, 2023
- Last OEM Support
- May 18, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Jira Software 8.17 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Jira Software 8.17?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Jira Software 8.17 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Jira Software 8.17 Support: Frequently Asked Questions
Is the Jira Software 8.17 still supported?
Jira Software ended support for the Jira Software 8.17 on May 18, 2023 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Jira Software 8.17 end of service life (EOSL) date?
Jira Software lists the end of service life for the Jira Software 8.17 as May 18, 2023.
Can I keep using the Jira Software 8.17 after its EOSL date?
Yes. EOSL means Jira Software stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Jira Software 8.17 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Jira Software 8.17
7 published CVEs affect the Jira Software 8.17, including 2 rated critical or high severity. Jira Software no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2017-18113 | HIGH | 8.8 | Aug 2, 2021 | The DefaultOSWorkflowConfigurator class in Jira Server and Jira Data Center before version 8.18.1 allows remote attackers who can trick a system administrator to import their malicious workflow to execute arbitrary code via a Remote Code Execution (RCE) vulnerability. The vulnerability allowed for various problematic OSWorkflow classes to be used as part of workflows. The fix for this issue blocks usage of unsafe conditions, validators, functions and registers that are build-in into OSWorkflow l |
| CVE-2021-41312 | HIGH | 7.5 | Nov 3, 2021 | Affected versions of Atlassian Jira Server and Data Center allow a remote attacker who has had their access revoked from Jira Service Management to enable and disable Issue Collectors on Jira Service Management projects via an Improper Authentication vulnerability in the /secure/ViewCollectors endpoint. The affected versions are before version 8.19.1. |
| CVE-2021-39118 | MEDIUM | 5.3 | Sep 14, 2021 | Affected versions of Atlassian Jira Server and Data Center allow remote attackers to discover the usernames and full names of users via an enumeration vulnerability in the /rest/api/1.0/render endpoint. The affected versions are before version 8.19.0. |
| CVE-2021-39119 | MEDIUM | 5.3 | Sep 1, 2021 | Affected versions of Atlassian Jira Server and Data Center allow users who have watched an issue to continue receiving updates on the issue even after their Jira account is revoked, via a Broken Access Control vulnerability in the issue notification feature. The affected versions are before version 8.19.0. |
| CVE-2021-43945 | MEDIUM | 4.8 | Feb 28, 2022 | Affected versions of Atlassian Jira Server and Data Center allow remote attackers with Roadmaps Administrator permissions to inject arbitrary HTML or JavaScript via a Stored Cross-Site Scripting (SXSS) vulnerability in the /rest/jpo/1.0/hierarchyConfiguration endpoint. The affected versions are before version 8.20.3. |
| CVE-2021-39117 | MEDIUM | 4.8 | Aug 30, 2021 | The AssociateFieldToScreens page in Atlassian Jira Server and Data Center before version 8.18.0 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability via the name of a custom field. |
| CVE-2021-43953 | MEDIUM | 4.3 | Feb 15, 2022 | Affected versions of Atlassian Jira Server and Data Center allow unauthenticated remote attackers to toggle the Thread Contention and CPU monitoring settings via a Cross-Site Request Forgery (CSRF) vulnerability in the /secure/admin/ViewInstrumentation.jspa endpoint. The affected versions are before version 8.13.16, and from version 8.14.0 before 8.20.5. |