# CVE-2022-33068: Integer overflow in n/a > An integer overflow in Harfbuzz allows attackers to cause a Denial of Service via unspecified vectors. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Jun 2022 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2022-33068, ALSA-2022:8384, DEBIAN-CVE-2022-33068, GHSA-cq67-chj5-8385, OESA-2022-1777, RHSA-2022:8384, RLSA-2022:8384, ROOT-OS-DEBIAN-11-CVE-2022-33068, SUSE-SU-2022:2663-1, SUSE-SU-2022:2664-1, UBUNTU-CVE-2022-33068, USN-5524-1, openSUSE-SU-2022:2663-1, openSUSE-SU-2024:12168-1 ## What is CVE-2022-33068? CVE-2022-33068 is a medium-severity vulnerability in Fedoraproject Fedora, published on 22 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description An integer overflow in the component hb-ot-shape-fallback.cc of Harfbuzz v4.3.0 allows attackers to cause a Denial of Service (DoS) via unspecified vectors. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2022-33068? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `harfbuzz` | AlmaLinux:9 | All versions | 2.7.4-8.el9 | | `harfbuzz-devel` | AlmaLinux:9 | All versions | 2.7.4-8.el9 | | `harfbuzz-icu` | AlmaLinux:9 | All versions | 2.7.4-8.el9 | | `harfbuzz` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-icu` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz-icu-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.7.4-8.el9 | | `harfbuzz` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.7.4-8.el9 | | `harfbuzz-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.7.4-8.el9 | | `harfbuzz-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.7.4-8.el9 | | `harfbuzz-devel-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.7.4-8.el9 | | `harfbuzz-icu-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.7.4-8.el9 | | `harfbuzz` | Rocky Linux:9 | All versions | 0:2.7.4-8.el9 | | `harfbuzz` | SUSE:Enterprise Storage 7 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 3.4.0-150400.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Server 15 SP2-BCL | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Manager Proxy 4.1 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Manager Retail Branch Server 4.1 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | SUSE:Manager Server 4.1 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | openSUSE:Leap 15.3 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | openSUSE:Leap 15.4 | All versions | 3.4.0-150400.3.3.1 | | `harfbuzz` | openSUSE:Leap Micro 5.2 | All versions | 2.6.4-150200.3.3.1 | | `harfbuzz` | openSUSE:Tumbleweed | All versions | 4.4.1-1.1 | Products: Fedoraproject Fedora, Harfbuzz Project Harfbuzz. ## How do I fix CVE-2022-33068? Upgrade to a fixed version. ## Is CVE-2022-33068 being exploited? There is no known exploitation of CVE-2022-33068 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-33068 and fix it if it is affected. What it is: CVE-2022-33068 is a medium-severity vulnerability in Fedoraproject Fedora, published on 22 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-33068 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. 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-2022-33068/ (Markdown: https://insights.sbomify.com/CVE-2022-33068/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-33068 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-33068 - OSV: https://osv.dev/vulnerability/CVE-2022-33068 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-33068/ Summaries are generated and may contain mistakes; the official description above is the record.