CVE Vulnerabilities

CVE-2023-50387

Allocation of Resources Without Limits or Throttling

Published: Feb 14, 2024 | 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
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the KeyTrap issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.

Weakness

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.

Affected Software

Name Vendor Start Version End Version
Enterprise_linux Redhat 6.0 (including) 6.0 (including)
Enterprise_linux Redhat 7.0 (including) 7.0 (including)
Enterprise_linux Redhat 8.0 (including) 8.0 (including)
Enterprise_linux Redhat 9.0 (including) 9.0 (including)
Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION RedHat bind-32:9.8.2-0.68.rc1.el6_10.14 *
Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION RedHat bind-dyndb-ldap-0:2.3-8.el6_10.1 *
Red Hat Enterprise Linux 7 RedHat bind-32:9.11.4-26.P2.el7_9.16 *
Red Hat Enterprise Linux 7 RedHat bind-dyndb-ldap-0:11.1-7.el7_9.1 *
Red Hat Enterprise Linux 7 RedHat dhcp-12:4.2.5-83.el7_9.2 *
Red Hat Enterprise Linux 7 Extended Lifecycle Support RedHat unbound-0:1.6.6-5.el7_9.1 *
Red Hat Enterprise Linux 8 RedHat unbound-0:1.16.2-5.el8_9.2 *
Red Hat Enterprise Linux 8 RedHat dnsmasq-0:2.79-31.el8_9.2 *
Red Hat Enterprise Linux 8 RedHat bind9.16-32:9.16.23-0.16.el8_9.2 *
Red Hat Enterprise Linux 8 RedHat bind-32:9.11.36-11.el8_9.1 *
Red Hat Enterprise Linux 8 RedHat bind-32:9.11.36-14.el8_10 *
Red Hat Enterprise Linux 8 RedHat bind-32:9.11.36-11.el8_9.1 *
Red Hat Enterprise Linux 8 RedHat bind-32:9.11.36-14.el8_10 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat unbound-0:1.7.3-12.el8_2.1 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat bind-32:9.11.13-6.el8_2.7 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat dhcp-12:4.3.6-40.el8_2.3 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat dnsmasq-0:2.79-11.el8_2.3 *
Red Hat Enterprise Linux 8.2 Telecommunications Update Service RedHat unbound-0:1.7.3-12.el8_2.1 *
Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions RedHat unbound-0:1.7.3-12.el8_2.1 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat unbound-0:1.7.3-15.el8_4.1 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat bind-32:9.11.26-4.el8_4.4 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat dhcp-12:4.3.6-44.el8_4.3 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat dnsmasq-0:2.79-15.el8_4.2 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat unbound-0:1.7.3-15.el8_4.1 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat bind-32:9.11.26-4.el8_4.4 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat dhcp-12:4.3.6-44.el8_4.3 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat dnsmasq-0:2.79-15.el8_4.2 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat unbound-0:1.7.3-15.el8_4.1 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat bind-32:9.11.26-4.el8_4.4 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat dhcp-12:4.3.6-44.el8_4.3 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat dnsmasq-0:2.79-15.el8_4.2 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat dnsmasq-0:2.79-21.el8_6.5 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat bind9.16-32:9.16.23-0.7.el8_6.5 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat unbound-0:1.7.3-17.el8_6.4 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat bind-32:9.11.36-3.el8_6.7 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat dhcp-12:4.3.6-47.el8_6.2 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat unbound-0:1.16.2-5.el8_8.1 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat dnsmasq-0:2.79-26.el8_8.4 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat bind9.16-32:9.16.23-0.14.el8_8.4 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat bind-32:9.11.36-8.el8_8.4 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat dhcp-12:4.3.6-49.el8_8.1 *
Red Hat Enterprise Linux 9 RedHat unbound-0:1.16.2-3.el9_3.1 *
Red Hat Enterprise Linux 9 RedHat dnsmasq-0:2.85-14.el9_3.1 *
Red Hat Enterprise Linux 9 RedHat bind-32:9.16.23-14.el9_3.4 *
Red Hat Enterprise Linux 9 RedHat bind-dyndb-ldap-0:11.9-8.el9_3.3 *
Red Hat Enterprise Linux 9 RedHat bind-32:9.16.23-18.el9_4.1 *
Red Hat Enterprise Linux 9 RedHat bind-dyndb-ldap-0:11.9-9.el9_4 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat dnsmasq-0:2.85-3.el9_0.1 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat bind-32:9.16.23-1.el9_0.5 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat bind-dyndb-ldap-0:11.9-7.el9_0.1 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat unbound-0:1.13.1-13.el9_0.4 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat unbound-0:1.16.2-3.el9_2.1 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat dnsmasq-0:2.85-6.el9_2.3 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat bind-32:9.16.23-11.el9_2.4 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat bind-dyndb-ldap-0:11.9-8.el9_2.2 *
Bind9 Ubuntu bionic *
Bind9 Ubuntu devel *
Bind9 Ubuntu esm-infra/bionic *
Bind9 Ubuntu esm-infra/xenial *
Bind9 Ubuntu focal *
Bind9 Ubuntu jammy *
Bind9 Ubuntu mantic *
Bind9 Ubuntu noble *
Bind9 Ubuntu oracular *
Bind9 Ubuntu trusty *
Bind9 Ubuntu trusty/esm *
Bind9 Ubuntu upstream *
Bind9 Ubuntu xenial *
Dnsmasq Ubuntu bionic *
Dnsmasq Ubuntu devel *
Dnsmasq Ubuntu esm-infra/bionic *
Dnsmasq Ubuntu esm-infra/xenial *
Dnsmasq Ubuntu focal *
Dnsmasq Ubuntu jammy *
Dnsmasq Ubuntu mantic *
Dnsmasq Ubuntu noble *
Dnsmasq Ubuntu oracular *
Dnsmasq Ubuntu trusty *
Dnsmasq Ubuntu trusty/esm *
Dnsmasq Ubuntu upstream *
Dnsmasq Ubuntu xenial *
Isc-dhcp Ubuntu mantic *
Knot-resolver Ubuntu bionic *
Knot-resolver Ubuntu esm-apps/noble *
Knot-resolver Ubuntu mantic *
Knot-resolver Ubuntu noble *
Knot-resolver Ubuntu upstream *
Knot-resolver Ubuntu xenial *
Pdns-recursor Ubuntu bionic *
Pdns-recursor Ubuntu esm-apps/noble *
Pdns-recursor Ubuntu mantic *
Pdns-recursor Ubuntu noble *
Pdns-recursor Ubuntu trusty *
Pdns-recursor Ubuntu upstream *
Pdns-recursor Ubuntu xenial *
Unbound Ubuntu bionic *
Unbound Ubuntu devel *
Unbound Ubuntu focal *
Unbound Ubuntu jammy *
Unbound Ubuntu mantic *
Unbound Ubuntu noble *
Unbound Ubuntu oracular *
Unbound Ubuntu trusty *
Unbound Ubuntu trusty/esm *
Unbound Ubuntu upstream *
Unbound Ubuntu xenial *

Extended Description

Code frequently has to work with limited resources, so programmers must be careful to ensure that resources are not consumed too quickly, or too easily. Without use of quotas, resource limits, or other protection mechanisms, it can be easy for an attacker to consume many resources by rapidly making many requests, or causing larger resources to be used than is needed. When too many resources are allocated, or if a single resource is too large, then it can prevent the code from working correctly, possibly leading to a denial of service.

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.

  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”

  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

  • 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 can be difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply requires more resources on the part of the attacker.

  • If the program must fail, ensure that it fails gracefully (fails closed). There may be a temptation to simply let the program fail poorly in cases such as low memory conditions, but an attacker may be able to assert control before the software has fully exited. Alternately, an uncontrolled failure could cause cascading problems with other downstream components; for example, the program could send a signal to a downstream process so the process immediately knows that a problem has occurred and has a better chance of recovery.

  • Ensure that all failures in resource allocation place the system into a safe posture.

  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.

  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.

  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References