REXML is an XML toolkit for Ruby. The REXML gem before 3.3.1 has some DoS vulnerabilities when it parses an XML that has many specific characters such as <, 0 and %>. If you need to parse untrusted XMLs, you many be impacted to these vulnerabilities. The REXML gem 3.3.2 or later include the patches to fix these vulnerabilities. Users are advised to upgrade. Users unable to upgrade should avoid parsing untrusted XML strings.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | RedHat | ruby:3.3-8100020240906074654.489197e6 | * |
| Red Hat Enterprise Linux 8 | RedHat | ruby:3.1-8100020250407112943.489197e6 | * |
| Red Hat Enterprise Linux 9 | RedHat | ruby:3.3-9040020240906110954.9 | * |
| Red Hat Enterprise Linux 9 | RedHat | ruby:3.1-9050020250404144903.9 | * |
| Jruby | Ubuntu | focal | * |
| Jruby | Ubuntu | oracular | * |
| Jruby | Ubuntu | trusty/esm | * |
| Ruby2.3 | Ubuntu | esm-infra/xenial | * |
| Ruby2.5 | Ubuntu | esm-infra/bionic | * |
| Ruby2.7 | Ubuntu | esm-infra/focal | * |
| Ruby2.7 | Ubuntu | focal | * |
| Ruby3.0 | Ubuntu | jammy | * |
| Ruby3.2 | Ubuntu | noble | * |
| Ruby3.3 | Ubuntu | oracular | * |
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.