CVE Vulnerabilities

CVE-2022-24729

Uncontrolled Resource Consumption

Published: Mar 16, 2022 | 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
Ubuntu
LOW

CKEditor4 is an open source what-you-see-is-what-you-get HTML editor. CKEditor4 prior to version 4.18.0 contains a vulnerability in the dialog plugin. The vulnerability allows abuse of a dialog input validator regular expression, which can cause a significant performance drop resulting in a browser tab freeze. A patch is available in version 4.18.0. There are currently no known workarounds.

Weakness

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

Affected Software

Name Vendor Start Version End Version
Ckeditor Ckeditor 4.0 (including) 4.18.0 (excluding)
Ckeditor Ubuntu bionic *
Ckeditor Ubuntu impish *
Ckeditor Ubuntu kinetic *
Ckeditor Ubuntu lunar *
Ckeditor Ubuntu mantic *
Ckeditor Ubuntu trusty *
Ckeditor Ubuntu upstream *
Ckeditor Ubuntu xenial *
Ckeditor3 Ubuntu bionic *
Ckeditor3 Ubuntu impish *
Ckeditor3 Ubuntu kinetic *
Ckeditor3 Ubuntu lunar *
Ckeditor3 Ubuntu mantic *
Ckeditor3 Ubuntu trusty *
Ckeditor3 Ubuntu xenial *
Ldap-account-manager Ubuntu bionic *
Ldap-account-manager Ubuntu impish *
Ldap-account-manager Ubuntu kinetic *
Ldap-account-manager Ubuntu lunar *
Ldap-account-manager Ubuntu mantic *
Ldap-account-manager Ubuntu trusty *
Ldap-account-manager Ubuntu xenial *
Request-tracker4 Ubuntu bionic *
Request-tracker4 Ubuntu impish *
Request-tracker4 Ubuntu kinetic *
Request-tracker4 Ubuntu lunar *
Request-tracker4 Ubuntu mantic *
Request-tracker4 Ubuntu trusty *
Request-tracker4 Ubuntu xenial *

Extended Description

Limited resources include memory, file system storage, database connection pool entries, and CPU. If an attacker can trigger the allocation of these limited resources, but the number or size of the resources is not controlled, then the attacker could cause a denial of service that consumes all available resources. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system. There are at least three distinct scenarios which can commonly lead to resource exhaustion:

Resource exhaustion problems are often result due to an incorrect implementation of the following situations:

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