CVE Vulnerabilities

CVE-2021-3481

Out-of-bounds Read

Published: Aug 22, 2022 | Modified: Aug 23, 2023
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7.1 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Ubuntu
LOW

A flaw was found in Qt. An out-of-bounds read vulnerability was found in QRadialFetchSimd in qt/qtbase/src/gui/painting/qdrawhelper_p.h in Qt/Qtbase. While rendering and displaying a crafted Scalable Vector Graphics (SVG) file this flaw may lead to an unauthorized memory access. The highest threat from this vulnerability is to data confidentiality and the application availability.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Qt Qt 5.15.1 (including) 5.15.1 (including)
Qt Qt 6.0.0 (including) 6.0.0 (including)
Qt Qt 6.0.2 (including) 6.0.2 (including)
Qt Qt 6.2.0 (including) 6.2.0 (including)
Red Hat Enterprise Linux 8 RedHat adwaita-qt-0:1.2.1-3.el8 *
Red Hat Enterprise Linux 8 RedHat python-qt5-0:5.15.0-2.el8 *
Red Hat Enterprise Linux 8 RedHat qgnomeplatform-0:0.7.1-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-0:5.15.2-1.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qt3d-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtbase-0:5.15.2-3.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtcanvas3d-0:5.12.5-3.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtconnectivity-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtdeclarative-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtdoc-0:5.15.2-1.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtgraphicaleffects-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtimageformats-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtlocation-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtmultimedia-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtquickcontrols-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtquickcontrols2-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtscript-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtsensors-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtserialbus-0:5.15.2-3.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtserialport-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtsvg-0:5.15.2-3.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qttools-0:5.15.2-3.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qttranslations-0:5.15.2-1.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtwayland-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtwebchannel-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtwebsockets-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtx11extras-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat qt5-qtxmlpatterns-0:5.15.2-2.el8 *
Red Hat Enterprise Linux 8 RedHat sip-0:4.19.24-2.el8 *
Qt4-x11 Ubuntu bionic *
Qt4-x11 Ubuntu trusty *
Qt4-x11 Ubuntu xenial *
Qtsvg-opensource-src Ubuntu bionic *
Qtsvg-opensource-src Ubuntu groovy *
Qtsvg-opensource-src Ubuntu hirsute *
Qtsvg-opensource-src Ubuntu impish *
Qtsvg-opensource-src Ubuntu kinetic *
Qtsvg-opensource-src Ubuntu lunar *
Qtsvg-opensource-src Ubuntu mantic *
Qtsvg-opensource-src Ubuntu trusty *
Qtsvg-opensource-src Ubuntu xenial *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References