# CVE-2023-46316: Command injection in n/a > Improper command line parsing in Traceroute wrapper scripts allows attackers to execute arbitrary commands. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 24 Oct 2023 - **Updated:** 2 Aug 2024 - **Also known as:** ALSA-2024:2483, ALSA-2024:3211, AZL-31746, CLSA-2025-1753299555, DEBIAN-CVE-2023-46316, GHSA-x3vv-qh4r-crf2, MGASA-2024-0168, OESA-2023-1784, RHSA-2024:2483, RHSA-2024:3211, RHSA-2025:0823, RLSA-2024:2483, RLSA-2024:3211, SUSE-SU-2023:4623-1, SUSE-SU-2023:4656-1, SUSE-SU-2024:2468-1, UBUNTU-CVE-2023-46316, USN-6478-1, openSUSE-SU-2024:13418-1 ## What is CVE-2023-46316? CVE-2023-46316 is a medium-severity command injection vulnerability in Debian Debian Linux, published on 24 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In buc Traceroute 2.0.12 through 2.1.2 before 2.1.3, the wrapper scripts do not properly parse command lines. Weakness: CWE-234 (Failure to Handle Missing Parameter) ## Which versions are affected by CVE-2023-46316? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `traceroute` | AlmaLinux:8 | All versions | 3:2.1.0-8.el8 | | `traceroute` | AlmaLinux:9 | All versions | 3:2.1.0-18.el9 | | `traceroute` | Red Hat:enterprise_linux:8::baseos | All versions | 3:2.1.0-8.el8 | | `traceroute-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 3:2.1.0-8.el8 | | `traceroute-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 3:2.1.0-8.el8 | | `traceroute` | Red Hat:enterprise_linux:9::baseos | All versions | 3:2.1.0-18.el9 | | `traceroute-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 3:2.1.0-18.el9 | | `traceroute-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 3:2.1.0-18.el9 | | `traceroute` | Red Hat:rhel_eus:8.8::baseos | All versions | 3:2.1.0-8.el8_8 | | `traceroute-debuginfo` | Red Hat:rhel_eus:8.8::baseos | All versions | 3:2.1.0-8.el8_8 | | `traceroute-debugsource` | Red Hat:rhel_eus:8.8::baseos | All versions | 3:2.1.0-8.el8_8 | | `traceroute` | Rocky Linux:8 | All versions | 3:2.1.0-8.el8 | | `traceroute` | Rocky Linux:9 | All versions | 3:2.1.0-18.el9 | | `traceroute` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.0.19-3.6.1 | | `traceroute` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.0.19-3.6.1 | | `traceroute` | openSUSE:Leap 15.4 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | openSUSE:Leap 15.5 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | openSUSE:Leap Micro 5.3 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | openSUSE:Leap Micro 5.4 | All versions | 2.0.21-150000.3.3.1 | | `traceroute` | openSUSE:Tumbleweed | All versions | 2.1.3-1.1 | Products: Buc Traceroute, Debian Debian Linux. ## How do I fix CVE-2023-46316? Upgrade to a fixed version. ## Is CVE-2023-46316 being exploited? There is no known exploitation of CVE-2023-46316 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-46316 and fix it if it is affected. What it is: CVE-2023-46316 is a medium-severity command injection vulnerability in Debian Debian Linux, published on 24 Oct 2023. 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-2023-46316 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-2023-46316/ (Markdown: https://insights.sbomify.com/CVE-2023-46316/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46316 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46316 - OSV: https://osv.dev/vulnerability/CVE-2023-46316 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-46316/ Summaries are generated and may contain mistakes; the official description above is the record.