CVE Vulnerabilities

CVE-2021-40797

Missing Release of Resource after Effective Lifetime

Published: Sep 08, 2021 | Modified: Sep 15, 2021
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:N/I:N/A:P
RedHat/V2
RedHat/V3
6.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

An issue was discovered in the routes middleware in OpenStack Neutron before 16.4.1, 17.x before 17.2.1, and 18.x before 18.1.1. By making API requests involving nonexistent controllers, an authenticated user may cause the API worker to consume increasing amounts of memory, resulting in API performance degradation or denial of service.

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
Neutron Openstack * 16.4.1 (excluding)
Neutron Openstack 17.0.0 (including) 17.2.1 (excluding)
Neutron Openstack 18.0.0 (including) 18.1.1 (excluding)
Red Hat OpenStack Platform 16.1 RedHat openstack-neutron-1:15.2.1-1.20220112133420.el8ost *
Red Hat OpenStack Platform 16.2 RedHat openstack-neutron-1:15.3.5-2.20220113150031.el8ost *
Neutron Ubuntu bionic *
Neutron Ubuntu focal *
Neutron Ubuntu hirsute *
Neutron Ubuntu trusty *
Neutron Ubuntu upstream *
Neutron Ubuntu xenial *

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