Loading
×Sorry to interrupt
CSS Error
Security Advisory

K000148809: Qt vulnerabilities CVE-2023-38197, CVE-2023-37369, and CVE-2023-32763

Security Advisory Description

  • CVE-2023-38197

    An issue was discovered in Qt before 5.15.15, 6.x before 6.2.10, and 6.3.x through 6.5.x before 6.5.3. There are infinite loops in recursive entity expansion.

  • CVE-2023-37369

    In Qt before 5.15.15, 6.x before 6.2.9, and 6.3.x through 6.5.x before 6.5.2, there can be an application crash in QXmlStreamReader via a crafted XML string that triggers a situation in which a prefix is greater than a length.

  • CVE-2023-32763

    An issue was discovered in Qt before 5.15.15, 6.x before 6.2.9, and 6.3.x through 6.5.x before 6.5.1. When a SVG file with an image inside it is rendered, a QTextLayout buffer overflow can be triggered.

Impact

An attacker may be able to exploit this vulnerability to cause an unexpected consumption of resources, such as CPU cycles or memory.

Security Advisory Status

F5 Product Development has assigned IDs 1596073, 1596097, and 1600233 (BIG-IP) and IDs 1593425 and 1593413 (APM Clients) to this vulnerability.

To determine if your product and version have been evaluated for this vulnerability, refer to the Evaluated products box. To determine if your release is known to be vulnerable, the components or features that are affected by the vulnerability, and for information about releases, point releases, or hotfixes that address the vulnerability, refer to the following tables. You can also use iHealth to diagnose a vulnerability for BIG-IP and BIG-IQ systems. For more information about using iHealth, refer to K27404821: Using F5 iHealth to diagnose vulnerabilities. For more information about security advisory versioning, refer to K51812227: Understanding security advisory versioning.

In this section

BIG-IP Next

Note: After a fix is introduced for a given minor branch, that fix applies to all subsequent maintenance and point releases for that branch, and no additional fixes for that branch will be listed in the table. For example, when a fix is introduced in 20.0.2, the fix also applies to 20.0.3, and all later 20.1.x releases. For more information, refer to K51812227: Understanding security advisory versioning.

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverity/CVSS scoreVulnerable component or feature
BIG-IP Next (all modules)AllNoneNot applicableNot vulnerableNone
BIG-IP Next Central ManagerAllNoneNot applicableNot vulnerableNone
BIG-IP Next SPKAllNoneNot applicableNot vulnerableNone
BIG-IP Next CNFAllNoneNot applicableNot vulnerableNone

1F5 evaluates only software versions that have not yet reached the End of Technical Support (EoTS) phase of their lifecycle. For more information, refer to the Security hotfixes section of K4602: Overview of the F5 security vulnerability response policy.

BIG-IP and BIG-IQ

Note: After a fix is introduced for a given minor branch, that fix applies to all subsequent maintenance and point releases for that branch, and no additional fixes for that branch will be listed in the table. For example, when a fix is introduced in 16.1.2.1, the fix also applies to 16.1.2.2, and all later 16.1.x releases (16.1.3.x, 16.1.4.x). For more information, refer to K51812227: Understanding security advisory versioning.

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverity/CVSS score2Vulnerable component or feature
BIG-IP (all modules)17.x17.1.0 - 17.1.1NoneMedium/6.5 (CVSS v3.1)iApps (Qt package)
16.x16.1.0 - 16.1.5None
15.x15.1.0 - 15.1.10None
APM Clients7.2.x7.2.4.6 - 7.2.4.77.2.4.8High/7.5 (CVSS v3.1)APM Clients3
BIG-IQ Centralized ManagementAllNoneNot applicableNot vulnerableNone

1F5 evaluates only software versions that have not yet reached the End of Technical Support (EoTS) phase of their lifecycle. For more information, refer to the Security hotfixes section of K4602: Overview of the F5 security vulnerability response policy.

2Starting with the August 2024 Quarterly Security Notification, F5 will provide the CVSS v4.0 base score in addition to the CVSS v3.1 score, for first-party security issues only. The CVSS score link takes you to a resource outside of MyF5, and the content may be removed without our knowledge. For more information about how F5 uses CVSS v4.0, refer to K000140363: Overview of CVSS v4.0 in F5 security advisories.

3The noted APM client versions are vulnerable to CVE-2023-38197 and CVE-2023-37369 and not vulnerable to CVE-2023-32763.

F5 Distributed Cloud and NGINX Services

ServiceSeverity/CVSS scoreVulnerable component or feature
F5 Distributed Cloud (all services)Not vulnerableNone
F5 Silverline (all services)Not vulnerableNone
NGINX One ConsoleNot vulnerableNone

F5OS

Product

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverity/CVSS scoreVulnerable component or feature
F5OS-AAllNoneNot applicableNot vulnerableNone
F5OS-CAllNoneNot applicableNot vulnerableNone

1F5 evaluates only software versions that have not yet reached the End of Technical Support (EoTS) phase of their lifecycle. For more information, refer to the Security hotfixes section of K4602: Overview of the F5 security vulnerability response policy.

NGINX

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverity/CVSS scoreVulnerable component or feature
NGINX (all products)AllNoneNot applicableNot vulnerableNone

1F5 evaluates only software versions that have not yet reached the End of Technical Support (EoTS) phase of their lifecycle. For more information, refer to the Security hotfixes section of K4602: Overview of the F5 security vulnerability response policy.

Other products

ProductBranchVersions known to be vulnerable1Fixes introduced inSeverity/CVSS scoreVulnerable component or feature
Traffix SDCAllNoneNot applicableNot vulnerableNone

1F5 evaluates only software versions that have not yet reached the End of Technical Support (EoTS) phase of their lifecycle. For more information, refer to the Security hotfixes section of K4602: Overview of the F5 security vulnerability response policy.

Security Advisory Recommended Actions

If you are running a version listed in the Versions known to be vulnerable column, you can eliminate this vulnerability by installing a version listed in the Fixes introduced in column. If the Fixes introduced in column does not list a version for your branch, then no update candidate currently exists for that branch and F5 recommends that you upgrade to a version with the fix (refer to the tables).

If the Fixes introduced in column lists a version prior to the one you are running, in the same branch, then your version should have the fix.

Mitigation

Do not process or handle data from untrusted sources.

Related Content

Loading