CVE Vulnerabilities

CVE-2023-36479

Improper Neutralization of Quoting Syntax

Published: Sep 15, 2023 | Modified: Oct 16, 2023
CVSS 3.x
4.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
3.5 LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N
Ubuntu
MEDIUM

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

Quotes injected into a product can be used to compromise a system. As data are parsed, an injected/absent/duplicate/malformed use of quotes may cause the process to take unexpected actions.

Affected Software

Name Vendor Start Version End Version
Jetty Eclipse 9.0.0 (including) 9.4.52 (excluding)
Jetty Eclipse 10.0.0 (including) 10.0.16 (excluding)
Jetty Eclipse 11.0.0 (including) 11.0.16 (excluding)
Jetty Eclipse 12.0.0-alpha1 (including) 12.0.0-alpha1 (including)
Jetty Eclipse 12.0.0-alpha2 (including) 12.0.0-alpha2 (including)
Jetty Eclipse 12.0.0-alpha3 (including) 12.0.0-alpha3 (including)
Jetty Eclipse 12.0.0-beta0 (including) 12.0.0-beta0 (including)
Jetty Eclipse 12.0.0-beta1 (including) 12.0.0-beta1 (including)
Migration Toolkit for Runtimes 1 on RHEL 8 RedHat mtr/mtr-operator-bundle:1.2-23 *
Migration Toolkit for Runtimes 1 on RHEL 8 RedHat mtr/mtr-rhel8-operator:1.2-15 *
Migration Toolkit for Runtimes 1 on RHEL 8 RedHat mtr/mtr-web-container-rhel8:1.2-16 *
Migration Toolkit for Runtimes 1 on RHEL 8 RedHat mtr/mtr-web-executor-container-rhel8:1.2-14 *
MTA-6.2-RHEL-9 RedHat mta/mta-windup-addon-rhel9:6.2.3-2 *
Red Hat Fuse 7.12.1 RedHat jetty-servlets *
Red Hat Fuse 7.13.0 RedHat jetty-servlets *
Red Hat Satellite 6.14 for RHEL 8 RedHat candlepin-0:4.3.11-1.el8sat *
Red Hat Satellite 6.15 for RHEL 8 RedHat puppetserver-0:7.14.0-1.el8sat *
Red Hat Satellite 6.15 for RHEL 8 RedHat puppetserver-0:7.14.0-1.el8sat *
Jetty Ubuntu bionic *
Jetty Ubuntu trusty *
Jetty Ubuntu xenial *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References