RT 4.4.4 and RT 4.2.16 Released


Best Practical is happy to announce the general availability of RT 4.4.4. This release contains important security updates, mostly in modules RT depends on. It also introduces several new features to help organizations comply with the EU’s new General Data Protection Regulation (GDPR) and a number of general updates and fixes.

RT 4.2.16 is a maintenance release for the RT 4.2 series and contains security updates, but does not include the new GDPR features. Upgrade to RT 4.4.4 to get access to the new features and many other features introduced in the RT 4.4 series.


GDPR Features

The EU’s new GDPR introduces new guidelines and legal requirements for the storage and handling of user information. Depending on how you use RT, it can contain contact information for end users like email address and potentially additional data. Several new features were added to RT to help administrators work with potential requests from end users.

  • New ways to download user data to format-neutral tsv files.

  • Options to anonymize or remove users.

  • A tool to remove PII from transaction history.

  • Allow self service users to optionally view and edit their personal data.

New options to manage user data in RT

New options to manage user data in RT

Many of these features can be selectively enabled so each administrator can use only the features they need to comply with their organization’s policies. The new GDPR documentation contains more details on the new features.

Security Updates

The following security updates apply to both RT 4.4.4 and RT 4.2.16. Note that most are in dependencies of RT and not RT directly, so new versions of the noted modules need to be updated in addition to updating RT.

  • One of RT’s dependencies, the Perl module Email::Address, has a denial of service vulnerability which could induce a denial of service of RT itself. We recommend updating to Email::Address version 1.912 or later. The Email::Address vulnerabilities are assigned CVE-2015-7686 and CVE-2015-12558. CVE-2015-7686 was addressed in RT with a previous update. Email::Address version 1.912 addresses both of these CVEs with updates directly in the source module. Thanks to Ricardo Signes for helping us with these updates.

  • One of RT’s dependencies, the Perl module Email::Address::List, relies on and operates similarly to Email::Address and therefore also has potential denial of service vulnerabilities. These vulnerabilities are assigned CVE-2018-18898. We recommend administrators install Email::Address::List version 0.06 or later. Thanks to Lukas Kramer for reporting the issue and Alex Vandiver for contributing fixes.

  • An optional RT dependency, HTML::Gumbo, incorrectly escaped HTML in some cases. Since RT relies on this module to escape HTML content, it’s possible this issue could allow malicious HTML to be displayed in RT. For RT’s using this optional module, we recommend administrators install HTML::Gumbo version 0.18 or later. Thanks to Ruslan Zakirov for updating this module.

  • The version of jQuery used in RT 4.2 and 4.4 has a Cross-site Scripting (XSS) vulnerability when using cross-domain Ajax requests. This vulnerability is assigned CVE-2015-9251. RT does not use this jQuery feature so it is not directly vulnerable. jQuery version 1.12 no longer receives official updates, however a fix was posted with recommendations for applications to patch locally, so RT will follow this recommendation and ship with a patched version.

Detailed release notes are available for RT 4.4.4 and RT 4.2.16.

Instructions for updating RT are provided in the README files for each release. Always make sure you have known good database and file backups before upgrading. Contact Best Practical at sales@bestpractical.com if you need professional assistance with upgrading from any previous versions of RT.

Share this post: