# CVE-2023-36479: Jetty vulnerable to errant command quoting in CGI Servlet > Attackers can execute arbitrary commands via the CGI Servlet if specific quoting flaws are triggered, requiring users to upgrade Jetty. - **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Sep 2023 - **Updated:** 18 Jun 2025 - **Also known as:** CLEANSTART-2026-GQ19104, CLEANSTART-2026-HP29225, CLSA-2026-1785926105, DEBIAN-CVE-2023-36479, GHSA-3gh6-v5v9-6v9j, UBUNTU-CVE-2023-36479 ## What is CVE-2023-36479? CVE-2023-36479 is a low-severity command injection vulnerability in Debian Debian Linux, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Eclipse Jetty Canonical Repository is the canonical repository for the Jetty project. Users of the CgiServlet with a very specific command structure may have the wrong command executed. If a user sends a request to a org.eclipse.jetty.servlets.CGI Servlet for a binary with a space in its name, the servlet will escape the command by wrapping it in quotation marks. This wrapped command, plus an optional command prefix, will then be executed through a call to Runtime.exec. If the original binary name provided by the user contains a quotation mark followed by a space, the resulting command line will contain multiple tokens instead of one. This issue was patched in version 9.4.52, 10.0.16, 11.0.16 and 12.0.0-beta2. Weakness: CWE-149 (Improper Neutralization of Quoting Syntax) ## Which versions are affected by CVE-2023-36479? 12 open source packages ship an affected version, including org.eclipse.jetty:jetty-servlets, org.eclipse.jetty.ee10:jetty-ee10-servlets and org.eclipse.jetty.ee8:jetty-ee8-servlets. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.jetty:jetty-servlets` | Maven | From 10.0.0 | 10.0.16 | | `org.eclipse.jetty:jetty-servlets` | Maven | From 10.0.0 | 10.0.16 | | `org.eclipse.jetty:jetty-servlets` | Maven | From 11.0.0 | 11.0.16 | | `org.eclipse.jetty:jetty-servlets` | Maven | From 11.0.0 | 11.0.16 | | `org.eclipse.jetty:jetty-servlets` | Maven | From 9.0.0 | 9.4.52 | | `org.eclipse.jetty:jetty-servlets` | Maven | From 9.0.0 | 9.4.52 | | `org.eclipse.jetty.ee10:jetty-ee10-servlets` | Maven | All versions | 12.0.0-beta2 | | `org.eclipse.jetty.ee10:jetty-ee10-servlets` | Maven | All versions | 12.0.0-beta2 | | `org.eclipse.jetty.ee8:jetty-ee8-servlets` | Maven | All versions | 12.0.0-beta2 | | `org.eclipse.jetty.ee8:jetty-ee8-servlets` | Maven | All versions | 12.0.0-beta2 | | `org.eclipse.jetty.ee9:jetty-ee9-servlets` | Maven | All versions | 12.0.0-beta2 | | `org.eclipse.jetty.ee9:jetty-ee9-servlets` | Maven | All versions | 12.0.0-beta2 | Products: Debian Debian Linux, Eclipse Jetty. ## How do I fix CVE-2023-36479? Upgrade org.eclipse.jetty:jetty-servlets to a fixed version for your release line: 10.0.16, 11.0.16 or 9.4.52. ## Is CVE-2023-36479 being exploited? There is no known exploitation of CVE-2023-36479 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-36479 and fix it if it is affected. What it is: CVE-2023-36479 is a low-severity command injection vulnerability in Debian Debian Linux, published on 15 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-36479 in the wild and no public exploit code. Affected packages and fixed versions: - org.eclipse.jetty:jetty-servlets (Maven): affected from 10.0.0; fixed in 10.0.16 - org.eclipse.jetty:jetty-servlets (Maven): affected from 10.0.0; fixed in 10.0.16 - org.eclipse.jetty:jetty-servlets (Maven): affected from 11.0.0; fixed in 11.0.16 - org.eclipse.jetty:jetty-servlets (Maven): affected from 11.0.0; fixed in 11.0.16 - org.eclipse.jetty:jetty-servlets (Maven): affected from 9.0.0; fixed in 9.4.52 - org.eclipse.jetty:jetty-servlets (Maven): affected from 9.0.0; fixed in 9.4.52 - org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 - org.eclipse.jetty.ee10:jetty-ee10-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 - org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 - org.eclipse.jetty.ee8:jetty-ee8-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 - org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 - org.eclipse.jetty.ee9:jetty-ee9-servlets (Maven): affected all versions; fixed in 12.0.0-beta2 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-36479/ (Markdown: https://insights.sbomify.com/CVE-2023-36479/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-36479 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-36479 - OSV: https://osv.dev/vulnerability/CVE-2023-36479 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-36479/ Summaries are generated and may contain mistakes; the official description above is the record.