CVE Vulnerabilities

CVE-2021-32740

Uncontrolled Resource Consumption

Published: Jul 06, 2021 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
LOW

Addressable is an alternative implementation to the URI implementation that is part of Rubys standard library. An uncontrolled resource consumption vulnerability exists after version 2.3.0 through version 2.7.0. Within the URI template implementation in Addressable, a maliciously crafted template may result in uncontrolled resource consumption, leading to denial of service when matched against a URI. In typical usage, templates would not normally be read from untrusted user input, but nonetheless, no previous security advisory for Addressable has cautioned against doing this. Users of the parsing capabilities in Addressable but not the URI template capabilities are unaffected. The vulnerability is patched in version 2.8.0. As a workaround, only create Template objects from trusted sources that have been validated not to produce catastrophic backtracking.

Weakness

The product does not properly control the allocation and maintenance of a limited resource.

Affected Software

Name Vendor Start Version End Version
Addressable Addressable_project 2.3.0 (including) 2.8.0 (excluding)
OpenShift Logging 5.2 RedHat openshift-logging/fluentd-rhel8:v5.2.0-10 *
Red Hat Satellite 6.10 for RHEL 7 RedHat tfm-rubygem-addressable-0:2.8.0-1.el7sat *
Ruby-addressable Ubuntu bionic *
Ruby-addressable Ubuntu focal *
Ruby-addressable Ubuntu groovy *
Ruby-addressable Ubuntu hirsute *
Ruby-addressable Ubuntu trusty *
Ruby-addressable Ubuntu upstream *
Ruby-addressable Ubuntu xenial *

Potential Mitigations

  • 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.

References