Redmine 4.0
Redmine 4.0
The Redmine 4.0 reached end of service life on Apr 26, 2021 — Redmine 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 Redmine 4.0 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
- redmine
- release
- 4.0
- product Label
- Redmine
- release Label
- 4.0
- codename
- lts
- latest Version
- 4.0.9
- release Date
- 2018-12-09
- maintained
- source Url
- https://endoflife.date/redmine
Lifecycle Dates
- End of Service Life
- Apr 26, 2021
- Last OEM Support
- Apr 26, 2021
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Redmine 4.0 — 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 Redmine 4.0?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Redmine 4.0 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.
Redmine 4.0 Support: Frequently Asked Questions
Is the Redmine 4.0 still supported?
Redmine ended support for the Redmine 4.0 on Apr 26, 2021 — 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 Redmine 4.0 end of service life (EOSL) date?
Redmine lists the end of service life for the Redmine 4.0 as Apr 26, 2021.
Can I keep using the Redmine 4.0 after its EOSL date?
Yes. EOSL means Redmine 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 Redmine 4.0 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 Redmine 4.0
17 published CVEs affect the Redmine 4.0, including 3 rated critical or high severity. Redmine no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2021-30164 | CRITICAL | 9.8 | Apr 6, 2021 | Redmine before 4.0.8 and 4.1.x before 4.1.2 allows attackers to bypass the add_issue_notes permission requirement by leveraging the Issues API. |
| CVE-2021-31863 | HIGH | 7.5 | Apr 28, 2021 | Insufficient input validation in the Git repository integration of Redmine before 4.0.9, 4.1.x before 4.1.3, and 4.2.x before 4.2.1 allows Redmine users to read arbitrary local files accessible by the application server process. |
| CVE-2021-30163 | HIGH | 7.5 | Apr 6, 2021 | Redmine before 4.0.8 and 4.1.x before 4.1.2 allows attackers to discover the names of private projects if issue-journal details exist that have changes to project_id values. |
| CVE-2023-47260 | MEDIUM | 6.1 | Nov 5, 2023 | Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS via thumbnails. |
| CVE-2023-47259 | MEDIUM | 6.1 | Nov 5, 2023 | Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS in the Textile formatter. |
| CVE-2023-47258 | MEDIUM | 6.1 | Nov 5, 2023 | Redmine before 4.2.11 and 5.0.x before 5.0.6 allows XSS in a Markdown formatter. |
| CVE-2022-44637 | MEDIUM | 6.1 | Dec 12, 2022 | Redmine before 4.2.9 and 5.0.x before 5.0.4 allows persistent XSS in its Textile formatter due to improper sanitization in Redcloth3 Textile-formatted fields. Depending on the configuration, this may require login as a registered user. |
| CVE-2022-44031 | MEDIUM | 6.1 | Dec 12, 2022 | Redmine before 4.2.9 and 5.0.x before 5.0.4 allows persistent XSS in its Textile formatter due to improper sanitization of the blockquote syntax in Textile-formatted fields. |
| CVE-2020-36307 | MEDIUM | 6.1 | Apr 6, 2021 | Redmine before 4.0.7 and 4.1.x before 4.1.1 has stored XSS via textile inline links. |
| CVE-2020-36306 | MEDIUM | 6.1 | Apr 6, 2021 | Redmine before 4.0.7 and 4.1.x before 4.1.1 has XSS via the back_url field. |
| CVE-2019-17427 | MEDIUM | 6.1 | Oct 10, 2019 | In Redmine before 3.4.11 and 4.0.x before 4.0.4, persistent XSS exists due to textile formatting errors. |
| CVE-2021-42326 | MEDIUM | 5.3 | Oct 12, 2021 | Redmine before 4.1.5 and 4.2.x before 4.2.3 may disclose the names of users on activity views due to an insufficient access filter. |
| CVE-2021-31866 | MEDIUM | 5.3 | Apr 28, 2021 | Redmine before 4.0.9 and 4.1.x before 4.1.3 allows an attacker to learn the values of internal authentication keys by observing timing differences in string comparison operations within SysController and MailHandlerController. |
| CVE-2021-31865 | MEDIUM | 5.3 | Apr 28, 2021 | Redmine before 4.0.9, 4.1.x before 4.1.3, and 4.2.x before 4.2.1 allows users to circumvent the allowed filename extensions of uploaded attachments. |
| CVE-2021-31864 | MEDIUM | 5.3 | Apr 28, 2021 | Redmine before 4.0.9, 4.1.x before 4.1.3, and 4.2.x before 4.2.1 allows attackers to bypass the add_issue_notes permission requirement by leveraging the incoming mail handler. |
| CVE-2020-36308 | MEDIUM | 5.3 | Apr 6, 2021 | Redmine before 4.0.7 and 4.1.x before 4.1.1 allows attackers to discover the subject of a non-visible issue by performing a CSV export and reading time entries. |
| CVE-2019-25026 | MEDIUM | 5.3 | Apr 6, 2021 | Redmine before 3.4.13 and 4.x before 4.0.6 mishandles markup data during Textile formatting. |