CVE Vulnerabilities

CVE-2022-30123

Improper Neutralization of Escape, Meta, or Control Sequences

Published: Dec 05, 2022 | Modified: Nov 21, 2024
CVSS 3.x
10
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
10 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM

A sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell escape in the Lint and CommonLogger components of Rack.

Weakness

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.

Affected Software

Name Vendor Start Version End Version
Rack Rack_project * 2.0.9.1 (excluding)
Rack Rack_project 2.1.0 (including) 2.1.4.1 (excluding)
Rack Rack_project 2.2.0 (including) 2.2.3.1 (excluding)
Logging subsystem for Red Hat OpenShift 5.4 RedHat openshift-logging/fluentd-rhel8:v1.14.5-51 *
Red Hat Enterprise Linux 7 RedHat pcs-0:0.9.169-3.el7_9.3 *
Red Hat Gluster Storage 3.5 for RHEL 7 RedHat rubygem-rack-0:2.2.4-1.el7rhgs *
Ruby-rack Ubuntu bionic *
Ruby-rack Ubuntu esm-apps/bionic *
Ruby-rack Ubuntu esm-apps/focal *
Ruby-rack Ubuntu esm-apps/jammy *
Ruby-rack Ubuntu esm-apps/xenial *
Ruby-rack Ubuntu focal *
Ruby-rack Ubuntu impish *
Ruby-rack Ubuntu jammy *
Ruby-rack Ubuntu trusty/esm *
Ruby-rack Ubuntu upstream *
Ruby-rack 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