These new versions contain 4 important security fixes, including an access control issue introduced in Redmine 5.0 that allows an unauthenticated user to download all attachments associated with a WikiContentVersion, so upgrading as soon as possible is highly recommended. You can review the Security_Advisories for more information.
Many thanks to all contributors that worked on the fixes and to Robert Dick, Frans Rosén, Noriko Totsuka from JPCERT/CC, Shiga Takuma of BroadBand Security, Inc. and Holger Just for reporting the security issues!
These new versions contain an important fix for a performance problem found in Redmine 4.2.7 and 5.0.2 (#37268) when database is Postgres and queries are filtered by a custom field value.Other fixes/updates:
- Mention auto-complete not works in bulk-edit comments (#37369)
- Common Markdown Formatter does not render all properties on HTML elements (#37237)
- Updates to latest Rails versions (#37465 - 184.108.40.206 and #37452 - 6.1.7) with security fixes
- Updates to latest jQuery 3.6.1 and jQuery UI 1.13.2 (security fixes)
Many thanks to all contributors that worked on the releases.
These maintenance releases fixes some important issues and multiple security fixes that were found in the latest Redmine 4.2.* and 5.0.* versions.Security:
- Updates commonmark gem version to 0.23.4 when Ruby >= 2.6 is used in order to fix a remote code execution vulnerability. Because the fixed version of the gem doesn't support Ruby 2.5, those instances that are using Redmine 5.0.*, Commonmark and Ruby 2.5, it is highly recommended to update Ruby version to at least 2.6 because it's the only way to get the update and the fix. Also, the next major Redmine version (5.1.0) already dropped support for Ruby 2.5 (#37159).
- Updates jQuery UI to 1.31.1 to fix 3 medium severity XSS vulnerabilities
- Fixes unauthorised Information Leak in QueryAssociationColumn and QueryAssociationCustomFieldColumn when the user has no permission to view on the associated object
Many thanks to Liane Hampe and Felix Schäfer for reporting these security issues and to Holger Just and Felix Schäfer for their work on fixing all these issues.
- an update to the latest Ruby on Rails 5.2.8 for 4.2.6 and Rails 6.1.6 for 5.0.1 that fixes CVE-2022-22577 and CVS-2022-27777.
- an update to nokogiri gem that fixes another 2 CVEs: CVE-2021-41098 and CVE-2021-30560
Thanks to A Fora for reporting the nokogiri security issues and all the contributors who worked on these releases!
- Migrate to Rails 6.1 with Zeitwerk autoloading (#29914). Switching to Zeitwerk autoloader breaks some plugins and requires plugin developers to fix the compatibility issues.
- Introduced CommonMark Markdown (GitHub Flavored) formatter (#32424) as an alternative to existing Markdown formatter based on Redcarpet. This new formatter is marked as experimental for now, but without any known issue. In the future versions, the Markdown based on Redcarpet will be deprecated and removed. A new configuration (
common_mark_enable_hardbreaks) was added to the configuration file (
configuration.yml) that allows to configure the hardbreak behaviour. Also, this formatter contains many fixes/improvements and supports task list items (#35742). Switching to this formatter is recommended for existing Markdown (there are some migration tips in the ticket).
- Users can be mention now using arobase autocomplete by other users with add watchers permission (#13919). This a long awaited feature.
- Issue custom query: default query per instance, project and user (#7360). This a long awaited feature.
- Default project custom query: per instance and per user (#35795).
- Ability to add watchers to Wiki pages (#7652).
- Issues can now be filtered by notes (#5893) or by file description (#34715).
- "Contains" operator supports now multiple search items (#35764). Using wilcard characters (_ or %) is no longer supported (#35073).
- Two-factor authentication improvements: you can enable it only for certain groups (#31920) or for users with administration rights (#35439). Users list contains now the 2FA status as column and as filter option (#35934).
Please review all the changes in the Changelog.
Please note that 4.1.7 is the last release for 4.1 series, you should upgrade to Redmine 4.2 or 5.0 to get the future maintenance updates.
Many thanks to Go Maeda, Mizuki ISHIKAWA, Takashi Kato, Bernhard Rohloff, Plan.io team, Pavel Rosický and all the contributors who made this release possible.
Security: these 2 releases include an update to the latest Ruby on Rails 5.2.* version that fixes CVE-2022-23633.
Thanks to all the contributors who worked on these releases.
1 These releases are not available yet on the releases page from a technical reason, we are sorry for this and we expect to have them uploaded next week. I'll post here an update after we have them uploaded.
Security: these 2 releases include a fix for a moderate severity issue found in all recent releases, so upgrading as soon as possible is recommended. You can get more details in Security Advisories.
Many thanks to Mischa The Evil for reporting and fixing this security issue!
Security: these 2 releases include an update to Ruby on Rails 5.2.6 version that fixes multiple vulnerability issues. Version 4.2.2 includes a fix for a low severity issue found in the 2FA feature, so upgrading as soon as possible is recommanded.
You can get more details in Security Advisories.
Many thanks to Felix Schäfer and Holger Just for reporting and fixing this security issue!
Security: these 3 releases include 4 security fixes, including a critical fix for an arbitrary file read in Git adapter, so upgrading as soon as possible is highly recommended. For those who cannot update immediately, another method to mitigate the critical risk is to update the Git version from the server to at least 2.22.0. You can get more details in Security Advisories.
Many thanks to niubl from TSRC (Tencent Security Response Center) for reporting this issue to the Redmine security team, to Holger Just from www.plan.io for the hard working on these security issues and to Go Maeda who made these releases possible.
Beside this, these new versions clarify and properly fix some inconsistent permissions for
add_issue_notes. Before 3.3.0, users only with
issue_edit permission were allowed to add notes to issues by design, but this behaviour changed when tracker role-based permissions were added (#285) and the
add_issue_notes was explicitly required in the UI. 4.0.8 extended this behaviour to API and 4.0.9 to mail handler. Please check your roles settings if you have the incoming email configured.
Also available in: Atom