# CVE-2022-48174: Memory corruption in n/a > A stack overflow in BusyBox ash allows arbitrary code execution, impacting Internet of Vehicles environments and embedded systems. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 22 Aug 2023 - **Updated:** 14 Jul 2026 - **Also known as:** ALPINE-CVE-2022-48174, AZL-56490, AZL-64326, BELL-CVE-2022-48174, CLEANSTART-2026-ZR79316, CLSA-2023-1693904834, CLSA-2023-1693904973, CLSA-2023-1693905084, CLSA-2023-1693906015, CLSA-2025-1760982550, DEBIAN-CVE-2022-48174, ECHO-189b-1da3-c996, GHSA-w9cc-xrp8-ffx4, OESA-2023-1583, RHSA-2023:5178, ROOT-OS-ALPINE-315-CVE-2022-48174, ROOT-OS-ALPINE-317-CVE-2022-48174, SUSE-SU-2023:3529-1, SUSE-SU-2023:3729-1, SUSE-SU-2023:3819-1, SUSE-SU-2023:3820-1, UBUNTU-CVE-2022-48174, openSUSE-SU-2024:13181-1 ## What is CVE-2022-48174? CVE-2022-48174 is a critical memory corruption vulnerability in Debian Debian Linux, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2022-48174? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `busybox` | Red Hat:rhel_els:6 | All versions | 1:1.15.1-21.el6_10.1 | | `busybox-petitboot` | Red Hat:rhel_els:6 | All versions | 1:1.15.1-21.el6_10.1 | | `busybox` | SUSE:Enterprise Storage 7 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Enterprise Storage 7.1 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.35.0-150400.3.11.1 | | `busybox` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 1.35.0-150500.10.3.3 | | `busybox` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.35.0-4.12.1 | | `busybox` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.35.0-4.12.1 | | `busybox` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Manager Proxy 4.2 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | SUSE:Manager Server 4.2 | All versions | 1.35.0-150000.4.20.1 | | `busybox` | openSUSE:Leap 15.4 | All versions | 1.35.0-150400.3.11.1 | | `busybox-links` | openSUSE:Leap 15.4 | All versions | 1.35.0-150400.4.5.1 | | `busybox` | openSUSE:Leap 15.5 | All versions | 1.35.0-150500.10.3.3 | | `busybox-links` | openSUSE:Leap 15.5 | All versions | 1.35.0-150400.4.5.1 | | `busybox` | openSUSE:Tumbleweed | All versions | 1.36.1-2.1 | Products: Busybox Busybox, Debian Debian Linux. ## How do I fix CVE-2022-48174? Upgrade to a fixed version. ## Is CVE-2022-48174 being exploited? There is no known exploitation of CVE-2022-48174 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8) - [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8) - [CVE-2022-28391](https://insights.sbomify.com/CVE-2022-28391/): Command injection in n/a (high 8.8) - [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8) - [CVE-2018-1000517](https://insights.sbomify.com/CVE-2018-1000517/): Memory corruption in n/a (high 8.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-48174 and fix it if it is affected. What it is: CVE-2022-48174 is a critical memory corruption vulnerability in Debian Debian Linux, published on 22 Aug 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-2022-48174 in the wild and no public exploit code. Affected product: Debian Debian Linux. 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-48174/ (Markdown: https://insights.sbomify.com/CVE-2022-48174/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48174 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48174 - OSV: https://osv.dev/vulnerability/CVE-2022-48174 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-48174/ Summaries are generated and may contain mistakes; the official description above is the record.