# CVE-2023-32763: Memory corruption in n/a > A buffer overflow in Qt's SVG rendering allows attackers to execute arbitrary code or cause denial of service via malicious SVG files. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 May 2023 - **Updated:** 2 Aug 2024 - **Also known as:** AZL-26877, CLEANSTART-2026-ES27254, DEBIAN-CVE-2023-32763, GHSA-j2m5-w7qp-hqg7, SUSE-SU-2023:2780-1, SUSE-SU-2023:2824-1, SUSE-SU-2023:2860-1, UBUNTU-CVE-2023-32763 ## What is CVE-2023-32763? CVE-2023-32763 is a high-severity memory corruption vulnerability in Qt Qt, published on 28 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2023-32763? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libqt5-qtbase` | SUSE:Enterprise Storage 7 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Enterprise Storage 7.1 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 5.15.8+kde185-150500.4.3.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 5.15.8+kde185-150500.4.3.1 | | `qt6-base` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 6.4.2-150500.3.3.1 | | `qt6-base` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 6.4.2-150500.3.3.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Manager Proxy 4.2 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | SUSE:Manager Server 4.2 | All versions | 5.12.7-150200.4.20.1 | | `libqt5-qtbase` | openSUSE:Leap 15.5 | All versions | 5.15.8+kde185-150500.4.3.1 | | `qt6-base` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.3.1 | | `qt6-base-docs` | openSUSE:Leap 15.5 | All versions | 6.4.2-150500.3.3.1 | Products: Qt Qt. ## How do I fix CVE-2023-32763? Upgrade to a fixed version. ## Is CVE-2023-32763 being exploited? There is no known exploitation of CVE-2023-32763 in the wild and no public exploit code. ## Other vulnerabilities in Qt Qt - [CVE-2020-12267](https://insights.sbomify.com/CVE-2020-12267/): Use after free in n/a (critical 9.8) - [CVE-2017-10904](https://insights.sbomify.com/CVE-2017-10904/): Command injection in Qt for Android (critical 9.8) - [CVE-2011-3194](https://insights.sbomify.com/CVE-2011-3194/): Memory corruption in n/a (critical 9.3) - [CVE-2022-40983](https://insights.sbomify.com/CVE-2022-40983/): Integer overflow in Qt (high 8.8) - [CVE-2022-43591](https://insights.sbomify.com/CVE-2022-43591/): Memory corruption in Qt (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-32763 and fix it if it is affected. What it is: CVE-2023-32763 is a high-severity memory corruption vulnerability in Qt Qt, published on 28 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-32763 in the wild and no public exploit code. Affected product: Qt Qt. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-32763/ (Markdown: https://insights.sbomify.com/CVE-2023-32763/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32763 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32763 - OSV: https://osv.dev/vulnerability/CVE-2023-32763 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-32763/ Summaries are generated and may contain mistakes; the official description above is the record.