CVE Vulnerabilities

CVE-2024-49769

Missing Release of Resource after Effective Lifetime

Published: Oct 29, 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

Waitress is a Web Server Gateway Interface server for Python 2 and 3. When a remote client closes the connection before waitress has had the opportunity to call getpeername() waitress wont correctly clean up the connection leading to the main thread attempting to write to a socket that no longer exists, but not removing it from the list of sockets to attempt to process. This leads to a busy-loop calling the write function. A remote attacker could run waitress out of available sockets with very little resources required. Waitress 3.0.1 contains fixes that remove the race condition.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Waitress Agendaless * 3.0.1 (excluding)
Ironic content for Red Hat OpenShift Container Platform 4.12 RedHat python-waitress-0:3.0.1-1.el9 *
Ironic content for Red Hat OpenShift Container Platform 4.13 RedHat python-waitress-0:3.0.1-1.el9 *
Red Hat OpenShift Container Platform 4.14 RedHat python-waitress-0:3.0.1-1.el9 *
Red Hat OpenShift Container Platform 4.15 RedHat python-waitress-0:3.0.1-1.el9 *
Red Hat OpenShift Container Platform 4.16 RedHat python-waitress-0:3.0.1-1.el9 *
Red Hat OpenShift Container Platform 4.17 RedHat python-waitress-0:3.0.1-1.el9 *
Red Hat OpenStack Platform 16.2 RedHat python-waitress-0:2.0.0-4.el8ost *
Waitress Ubuntu esm-apps/noble *
Waitress Ubuntu esm-infra/bionic *
Waitress Ubuntu esm-infra/xenial *
Waitress Ubuntu focal *
Waitress Ubuntu jammy *
Waitress Ubuntu noble *
Waitress Ubuntu oracular *
Waitress Ubuntu upstream *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • 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