# CVE-2022-33103: Memory corruption in n/a > An out-of-bounds write in the U-Boot bootloader allows attackers to execute arbitrary code or cause a denial of service. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jul 2022 - **Updated:** 3 Nov 2025 - **Also known as:** DEBIAN-CVE-2022-33103, GHSA-cxwr-rc7w-x3fr, OESA-2025-1574, OESA-2025-1575, SUSE-SU-2022:2868-1, SUSE-SU-2022:2869-1, UBUNTU-CVE-2022-33103 ## What is CVE-2022-33103? CVE-2022-33103 is a high-severity memory corruption vulnerability in n/a, published on 1 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Das U-Boot from v2020.10 to v2022.07-rc3 was discovered to contain an out-of-bounds write via the function sqfs_readdir(). Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2022-33103? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `u-boot` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-rpiarm64` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 2021.01-150300.7.18.1 | | `u-boot` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 2021.10-150400.4.11.1 | | `u-boot-rpiarm64` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 2021.10-150400.4.11.1 | | `u-boot` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-avnetultra96rev1` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-bananapim64` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-dragonboard410c` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-dragonboard820c` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-evb-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-firefly-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-geekbox` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-hikey` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-khadas-vim` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-khadas-vim2` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-libretech-ac` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-libretech-cc` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-ls1012afrdmqspi` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-mvebudb-88f3720` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-mvebudbarmada8k` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-mvebuespressobin-88f3720` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-mvebumcbin-88f8040` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-nanopia64` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-odroid-c2` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-odroid-c4` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-odroid-n2` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-orangepipc2` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-p2371-2180` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-p2771-0000-500` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-p3450-0000` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-pine64plus` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-pinebook` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-pinebook-pro-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-pineh64` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-pinephone` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-poplar` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-rock-pi-4-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-rock64-rk3328` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-rock960-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | | `u-boot-rockpro64-rk3399` | openSUSE:Leap 15.3 | All versions | 2021.01-150300.7.18.1 | Products: Denx U-Boot. ## How do I fix CVE-2022-33103? Apply the vendor's patch. ## Is CVE-2022-33103 being exploited? There is no known exploitation of CVE-2022-33103 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2022-34835](https://insights.sbomify.com/CVE-2022-34835/): Integer overflow in n/a (critical 9.8) - [CVE-2022-30767](https://insights.sbomify.com/CVE-2022-30767/): Memory corruption in n/a (critical 9.8) - [CVE-2020-8432](https://insights.sbomify.com/CVE-2020-8432/): Use after free in n/a (critical 9.8) - [CVE-2019-14192](https://insights.sbomify.com/CVE-2019-14192/): Integer overflow in n/a (critical 9.8) - [CVE-2019-14193](https://insights.sbomify.com/CVE-2019-14193/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-33103 and fix it if it is affected. What it is: CVE-2022-33103 is a high-severity memory corruption vulnerability in n/a, published on 1 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-33103 in the wild and no public exploit code. Affected product: n/a. 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-33103/ (Markdown: https://insights.sbomify.com/CVE-2022-33103/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-33103 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-33103 - OSV: https://osv.dev/vulnerability/CVE-2022-33103 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-33103/ Summaries are generated and may contain mistakes; the official description above is the record.