CVE Vulnerabilities

CVE-2023-0616

Uncontrolled Resource Consumption

Published: Jun 02, 2023 | Modified: Jan 10, 2025
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
4.3 LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Ubuntu
MEDIUM

If a MIME email combines OpenPGP and OpenPGP MIME data in a certain way Thunderbird repeatedly attempts to process and display the message, which could cause Thunderbirds user interface to lock up and no longer respond to the users actions. An attacker could send a crafted message with this structure to attempt a DoS attack. This vulnerability affects Thunderbird < 102.8.

Weakness

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

Affected Software

Name Vendor Start Version End Version
Thunderbird Mozilla * 102.8 (excluding)
Red Hat Enterprise Linux 7 RedHat thunderbird-0:102.8.0-2.el7_9 *
Red Hat Enterprise Linux 8 RedHat thunderbird-0:102.8.0-2.el8_7 *
Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions RedHat thunderbird-0:102.8.0-2.el8_1 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat thunderbird-0:102.8.0-2.el8_2 *
Red Hat Enterprise Linux 8.2 Telecommunications Update Service RedHat thunderbird-0:102.8.0-2.el8_2 *
Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions RedHat thunderbird-0:102.8.0-2.el8_2 *
Red Hat Enterprise Linux 8.4 Extended Update Support RedHat thunderbird-0:102.8.0-2.el8_4 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat thunderbird-0:102.8.0-2.el8_6 *
Red Hat Enterprise Linux 9 RedHat thunderbird-0:102.8.0-2.el9_1 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat thunderbird-0:102.8.0-2.el9_0 *
Thunderbird Ubuntu bionic *
Thunderbird Ubuntu focal *
Thunderbird Ubuntu jammy *
Thunderbird Ubuntu kinetic *
Thunderbird Ubuntu trusty *
Thunderbird Ubuntu upstream *
Thunderbird 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