A regular expression based DoS vulnerability in Active Support <6.1.7.1 and <7.0.4.1. 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.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Activesupport | Activesupport_project | * | 6.1.7.1 (excluding) |
| Activesupport | Activesupport_project | 7.0.0 (including) | 7.0.4.1 (excluding) |
| Red Hat Satellite 6.14 for RHEL 8 | RedHat | rubygem-activesupport-0:6.1.7.3-1.el8sat | * |
| RHOL-5.7-RHEL-8 | RedHat | openshift-logging/fluentd-rhel8:v1.14.6-152 | * |
| Rails | Ubuntu | bionic | * |
| Rails | Ubuntu | focal | * |
| Rails | Ubuntu | kinetic | * |
| Rails | Ubuntu | lunar | * |
| Rails | Ubuntu | mantic | * |
| Rails | Ubuntu | oracular | * |
| Rails | Ubuntu | trusty | * |
| Rails | Ubuntu | xenial | * |
| Rails-4.0 | Ubuntu | trusty | * |
| Ruby-actionpack-3.2 | Ubuntu | trusty | * |
| Ruby-activemodel-3.2 | Ubuntu | trusty | * |
| Ruby-activerecord-3.2 | Ubuntu | trusty | * |
| Ruby-activesupport-3.2 | Ubuntu | trusty | * |
| Ruby-rails-3.2 | Ubuntu | trusty | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.