Ruby/activesupport/5.2.4.1
A toolkit of support libraries and Ruby core extensions extracted from the Rails framework. Rich support for multibyte strings, internationalization, time zones, and testing.
https://rubygems.org/gems/activesupport
MIT
6 Security Vulnerabilities
ActiveSupport potentially unintended unmarshalling of user-provided objects in MemCacheStore and RedisCacheStore
- https://nvd.nist.gov/vuln/detail/CVE-2020-8165
- https://github.com/advisories/GHSA-2p68-f74v-9wc6
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activesupport/CVE-2020-8165.yml
- https://groups.google.com/forum/#!topic/rubyonrails-security/bv6fW4S0Y1c
- https://weblog.rubyonrails.org/2020/5/18/Rails-5-2-4-3-and-6-0-3-1-have-been-released/
- https://hackerone.com/reports/413388
- https://groups.google.com/g/rubyonrails-security/c/bv6fW4S0Y1c
- https://lists.debian.org/debian-lts-announce/2020/06/msg00022.html
- https://lists.debian.org/debian-lts-announce/2020/07/msg00013.html
- https://www.debian.org/security/2020/dsa-4766
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00031.html
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00034.html
In ActiveSupport, there is potentially unexpected behaviour in the MemCacheStore and RedisCacheStore where, when
untrusted user input is written to the cache store using the raw: true parameter, re-reading the result
from the cache can evaluate the user input as a Marshalled object instead of plain text. Vulnerable code looks like:
data = cache.fetch("demo", raw: true) { untrusted_string }
Versions Affected: rails < 5.2.5, rails < 6.0.4
Not affected: Applications not using MemCacheStore or RedisCacheStore. Applications that do not use the raw option when storing untrusted user input.
Fixed Versions: rails >= 5.2.4.3, rails >= 6.0.3.1
Impact
Unmarshalling of untrusted user input can have impact up to and including RCE. At a minimum,
this vulnerability allows an attacker to inject untrusted Ruby objects into a web application.
In addition to upgrading to the latest versions of Rails, developers should ensure that whenever
they are calling Rails.cache.fetch they are using consistent values of the raw parameter for both
reading and writing, especially in the case of the RedisCacheStore which does not, prior to these changes,
detect if data was serialized using the raw option upon deserialization.
Workarounds
It is recommended that application developers apply the suggested patch or upgrade to the latest release as
soon as possible. If this is not possible, we recommend ensuring that all user-provided strings cached using
the raw argument should be double-checked to ensure that they conform to the expected format.
Active Support Possibly Discloses Locally Encrypted Files
There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.
Versions Affected: >= 5.2.0 Not affected: < 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5
Impact
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file’s permissions are defaulted to the user’s current umask settings, meaning that it’s possible for other users on the same system to read the contents of the temporary file.
Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Releases
The fixed releases are available at the normal locations.
Workarounds
To work around this issue, you can set your umask to be more restrictive like this:
$ umask 0077
ReDoS based DoS vulnerability in Active Support's underscore
- https://github.com/rails/rails/releases/tag/v7.0.4.1
- https://github.com/advisories/GHSA-j6gc-792m-qgm2
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activesupport/CVE-2023-22796.yml
- https://rubyonrails.org/2023/1/17/Rails-Versions-6-0-6-1-6-1-7-1-7-0-4-1-have-been-released
- https://nvd.nist.gov/vuln/detail/CVE-2023-22796
- https://discuss.rubyonrails.org/t/cve-2023-22796-possible-redos-based-dos-vulnerability-in-active-supports-underscore/82116
- https://github.com/rails/rails/commit/2164d4f6a1bde74b911fe9ba3c8df1b5bf345bf8
- https://github.com/rails/rails/commit/a7cda7e6aa5334ab41b1f4b0f671be931be946ef
- https://github.com/rails/rails/releases/tag/v6.1.7.1
There is a possible regular expression based DoS vulnerability in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-22796.
Versions Affected: All Not affected: None Fixed Versions: 5.2.8.15 (Rails LTS, which is a paid service and not part of the rubygem), 6.1.7.1, 7.0.4.1 Impact
A specially crafted string passed to the underscore method can cause the regular expression engine to enter a state of catastrophic backtracking. This can cause the process to use large amounts of CPU and memory, leading to a possible DoS vulnerability.
This affects String#underscore, ActiveSupport::Inflector.underscore, String#titleize, and any other methods using these.
All users running an affected release should either upgrade or use one of the workarounds immediately. Releases
The FIXED releases are available at the normal locations. Workarounds
There are no feasible workarounds for this issue.
Users on Ruby 3.2.0 or greater may be able to reduce the impact by configuring Regexp.timeout. Patches
To aid users who aren’t able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.
6-1-Avoid-regex-backtracking-in-Inflector.underscore.patch - Patch for 6.1 series
7-0-Avoid-regex-backtracking-in-Inflector.underscore.patch - Patch for 7.0 series
Please note that only the 7.0.Z and 6.1.Z series are supported at present, and 6.0.Z for severe vulnerabilities. Users of earlier unsupported releases are advised to upgrade as soon as possible as we cannot guarantee the continued availability of security fixes for unsupported releases.
Possible XSS Security Vulnerability in SafeBuffer#bytesplice
- https://nvd.nist.gov/vuln/detail/CVE-2023-28120
- https://discuss.rubyonrails.org/t/cve-2023-28120-possible-xss-security-vulnerability-in-safebuffer-bytesplice/82469
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/activesupport/CVE-2023-28120.yml
- https://github.com/advisories/GHSA-pj73-v5mw-pm9j
There is a vulnerability in ActiveSupport if the new bytesplice method is called on a SafeBuffer with untrusted user input. This vulnerability has been assigned the CVE identifier CVE-2023-28120.
Versions Affected: All. Not affected: None Fixed Versions: 7.0.4.3, 6.1.7.3
Impact
ActiveSupport uses the SafeBuffer string subclass to tag strings as htmlsafe after they have been sanitized. When these strings are mutated, the tag is should be removed to mark them as no longer being htmlsafe.
Ruby 3.2 introduced a new bytesplice method which ActiveSupport did not yet understand to be a mutation. Users on older versions of Ruby are likely unaffected.
All users running an affected release and using bytesplice should either upgrade or use one of the workarounds immediately.
Workarounds
Avoid calling bytesplice on a SafeBuffer (html_safe) string with untrusted user input.
Possible XSS Security Vulnerability in SafeBuffer#bytesplice
There is a vulnerability in ActiveSupport if the new bytesplice method is called on a SafeBuffer with untrusted user input. This vulnerability has been assigned the CVE identifier CVE-2023-28120.
Versions Affected: All. Not affected: None Fixed Versions: 7.0.4.3, 6.1.7.3
Impact
ActiveSupport uses the SafeBuffer string subclass to tag strings as htmlsafe after they have been sanitized. When these strings are mutated, the tag is should be removed to mark them as no longer being htmlsafe.
Ruby 3.2 introduced a new bytesplice method which ActiveSupport did not yet understand to be a mutation. Users on older versions of Ruby are likely unaffected.
All users running an affected release and using bytesplice should either upgrade or use one of the workarounds immediately.
Workarounds
Avoid calling bytesplice on a SafeBuffer (html_safe) string with untrusted user input.
Possible File Disclosure of Locally Encrypted Files
There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.
Versions Affected: >= 5.2.0 Not affected: < 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5
Impact
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file’s permissions are defaulted to the user’s current umask settings, meaning that it’s possible for other users on the same system to read the contents of the temporary file.
Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Releases
The fixed releases are available at the normal locations.
Workarounds
To work around this issue, you can set your umask to be more restrictive like this:
$ umask 0077
477 Other Versions
| Version | License | Security | Released | |
|---|---|---|---|---|
| 8.0.0 | MIT | 2024-11-07 - 22:30 | 7 days | |
| 8.0.0.rc2 | MIT | 2024-10-30 - 00:31 | 16 days | |
| 8.0.0.rc1 | MIT | 2024-10-19 - 01:43 | 27 days | |
| 8.0.0.beta1 | MIT | 2024-09-26 - 15:05 | about 2 months | |
| 7.2.2 | MIT | 2024-10-31 - 01:47 | 15 days | |
| 7.2.1.2 | MIT | 2024-10-23 - 22:34 | 22 days | |
| 7.2.1.1 | MIT | 2024-10-15 - 20:46 | 30 days | |
| 7.2.1 | MIT | 2024-08-22 - 19:45 | 3 months | |
| 7.2.0 | MIT | 2024-08-09 - 23:26 | 3 months | |
| 7.2.0.rc1 | MIT | 2024-08-06 - 17:00 | 3 months | |
| 7.2.0.beta3 | MIT | 2024-07-11 - 15:19 | 4 months | |
| 7.2.0.beta2 | MIT | 2024-06-04 - 18:14 | 5 months | |
| 7.2.0.beta1 | MIT | 2024-05-29 - 23:37 | 6 months | |
| 7.1.5 | MIT | 2024-10-31 - 01:34 | 15 days | |
| 7.1.4.2 | MIT | 2024-10-23 - 22:28 | 22 days | |
| 7.1.4.1 | MIT | 2024-10-15 - 20:39 | 30 days | |
| 7.1.4 | MIT | 2024-08-22 - 21:26 | 3 months | |
| 7.1.3.4 | MIT | 2024-06-04 - 18:00 | 5 months | |
| 7.1.3.3 | MIT | 2024-05-16 - 19:21 | 6 months | |
| 7.1.3.2 | MIT | 2024-02-21 - 21:45 | 9 months | |
| 7.1.3.1 | MIT | 2024-02-21 - 18:46 | 9 months | |
| 7.1.3 | MIT | 2024-01-16 - 22:53 | 10 months | |
| 7.1.2 | MIT | 2023-11-10 - 21:49 | about 1 year | |
| 7.1.1 | MIT | 2023-10-11 - 22:16 | about 1 year | |
| 7.1.0 | MIT | 2023-10-05 - 08:06 | about 1 year | |
| 7.1.0.rc2 | MIT | 2023-10-01 - 21:59 | about 1 year | |
| 7.1.0.rc1 | MIT | 2023-09-27 - 04:00 | about 1 year | |
| 7.1.0.beta1 | MIT | 2023-09-13 - 00:36 | about 1 year | |
| 7.0.8.6 | MIT | 2024-10-23 - 22:23 | 22 days | |
| 7.0.8.5 | MIT | 2024-10-15 - 20:23 | 30 days | |
| 7.0.8.4 | MIT | 2024-06-04 - 17:56 | 5 months | |
| 7.0.8.3 | MIT | 2024-05-17 - 19:52 | 6 months | |
| 7.0.8.2 | MIT | 2024-05-16 - 18:57 | 6 months | |
| 7.0.8.1 | MIT | 2024-02-21 - 18:42 | 9 months | |
| 7.0.8 | MIT | 2023-09-09 - 19:10 | about 1 year | |
| 7.0.7.2 | MIT | 2023-08-22 - 20:10 | about 1 year | |
| 7.0.7.1 | MIT | 2023-08-22 - 17:20 | about 1 year | |
| 7.0.7 | MIT | 2 | 2023-08-09 - 23:56 | over 1 year |
| 7.0.6 | MIT | 2 | 2023-06-29 - 20:53 | over 1 year |
| 7.0.5.1 | MIT | 2 | 2023-06-26 - 21:35 | over 1 year |
| 7.0.5 | MIT | 2 | 2023-05-24 - 18:57 | over 1 year |
| 7.0.4.3 | MIT | 2 | 2023-03-13 - 18:53 | over 1 year |
| 7.0.4.2 | MIT | 4 | 2023-01-25 - 03:14 | almost 2 years |
| 7.0.4.1 | MIT | 4 | 2023-01-17 - 18:55 | almost 2 years |
| 7.0.4 | MIT | 6 | 2022-09-09 - 18:42 | about 2 years |
| 7.0.3.1 | MIT | 6 | 2022-07-12 - 17:31 | over 2 years |
| 7.0.3 | MIT | 6 | 2022-05-09 - 13:35 | over 2 years |
| 7.0.2.4 | MIT | 6 | 2022-04-26 - 19:33 | over 2 years |
| 7.0.2.3 | MIT | 6 | 2022-03-08 - 17:50 | over 2 years |
| 7.0.2.2 | MIT | 6 | 2022-02-11 - 19:43 | almost 3 years |
| 7.0.2.1 | MIT | 6 | 2022-02-11 - 18:18 | almost 3 years |
| 7.0.2 | MIT | 6 | 2022-02-08 - 23:11 | almost 3 years |
| 7.0.1 | MIT | 6 | 2022-01-06 - 21:53 | almost 3 years |
| 7.0.0 | MIT | 6 | 2021-12-15 - 23:42 | almost 3 years |
| 7.0.0.rc3 | MIT | 3 | 2021-12-14 - 23:04 | almost 3 years |
| 7.0.0.rc2 | MIT | 3 | 2021-12-14 - 19:39 | almost 3 years |
| 7.0.0.rc1 | MIT | 3 | 2021-12-06 - 21:28 | almost 3 years |
| 7.0.0.alpha2 | MIT | 3 | 2021-09-15 - 23:14 | about 3 years |
| 7.0.0.alpha1 | MIT | 3 | 2021-09-15 - 21:55 | about 3 years |
| 6.1.7.10 | MIT | 2024-10-23 - 21:58 | 22 days | |
| 6.1.7.9 | MIT | 2024-10-15 - 21:24 | 30 days | |
| 6.1.7.8 | MIT | 2024-06-04 - 17:55 | 5 months | |
| 6.1.7.7 | MIT | 2024-02-21 - 18:38 | 9 months | |
| 6.1.7.6 | MIT | 2023-08-22 - 20:07 | about 1 year | |
| 6.1.7.5 | MIT | 2023-08-22 - 17:15 | about 1 year | |
| 6.1.7.4 | MIT | 1 | 2023-06-26 - 21:31 | over 1 year |
| 6.1.7.3 | MIT | 1 | 2023-03-13 - 18:48 | over 1 year |
| 6.1.7.2 | MIT | 2 | 2023-01-25 - 03:23 | almost 2 years |
| 6.1.7.1 | MIT | 2 | 2023-01-17 - 18:54 | almost 2 years |
| 6.1.7 | MIT | 3 | 2022-09-09 - 18:38 | about 2 years |
| 6.1.6.1 | MIT | 3 | 2022-07-12 - 17:29 | over 2 years |
| 6.1.6 | MIT | 3 | 2022-05-09 - 13:44 | over 2 years |
| 6.1.5.1 | MIT | 3 | 2022-04-26 - 19:30 | over 2 years |
| 6.1.5 | MIT | 3 | 2022-03-10 - 21:12 | over 2 years |
| 6.1.4.7 | MIT | 3 | 2022-03-08 - 17:48 | over 2 years |
| 6.1.4.6 | MIT | 3 | 2022-02-11 - 19:41 | almost 3 years |
| 6.1.4.5 | MIT | 3 | 2022-02-11 - 18:22 | almost 3 years |
| 6.1.4.4 | MIT | 3 | 2021-12-15 - 22:52 | almost 3 years |
| 6.1.4.3 | MIT | 3 | 2021-12-14 - 23:02 | almost 3 years |
| 6.1.4.2 | MIT | 3 | 2021-12-14 - 19:45 | almost 3 years |
| 6.1.4.1 | MIT | 3 | 2021-08-19 - 16:25 | about 3 years |
| 6.1.4 | MIT | 3 | 2021-06-24 - 20:40 | over 3 years |
| 6.1.3.2 | MIT | 3 | 2021-05-05 - 15:34 | over 3 years |
| 6.1.3.1 | MIT | 3 | 2021-03-26 - 18:05 | over 3 years |
| 6.1.3 | MIT | 3 | 2021-02-17 - 18:41 | over 3 years |
| 6.1.2.1 | MIT | 3 | 2021-02-10 - 20:44 | almost 4 years |
| 6.1.2 | MIT | 3 | 2021-02-09 - 21:28 | almost 4 years |
| 6.1.1 | MIT | 3 | 2021-01-07 - 22:58 | almost 4 years |
| 6.1.0 | MIT | 3 | 2020-12-09 - 19:56 | almost 4 years |
| 6.1.0.rc2 | MIT | 3 | 2020-12-01 - 22:00 | almost 4 years |
| 6.1.0.rc1 | MIT | 3 | 2020-11-02 - 21:14 | about 4 years |
| 6.0.6.1 | MIT | 6 | 2023-01-17 - 18:52 | almost 2 years |
| 6.0.6 | MIT | 6 | 2022-09-09 - 18:31 | about 2 years |
| 6.0.5.1 | MIT | 6 | 2022-07-12 - 17:28 | over 2 years |
| 6.0.5 | MIT | 6 | 2022-05-09 - 13:50 | over 2 years |
| 6.0.4.8 | MIT | 6 | 2022-04-26 - 19:26 | over 2 years |
| 6.0.4.7 | MIT | 6 | 2022-03-08 - 17:47 | over 2 years |
| 6.0.4.6 | MIT | 6 | 2022-02-11 - 19:39 | almost 3 years |
| 6.0.4.5 | MIT | 6 | 2022-02-11 - 18:24 | almost 3 years |
| 6.0.4.4 | MIT | 6 | 2021-12-15 - 22:45 | almost 3 years |