CVE Vulnerabilities

CVE-2021-21707

Improper Handling of Invalid Use of Special Elements

Published: Nov 29, 2021 | Modified: Nov 21, 2024
CVSS 3.x
5.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.3 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Ubuntu
LOW

In PHP versions 7.3.x below 7.3.33, 7.4.x below 7.4.26 and 8.0.x below 8.0.13, certain XML parsing functions, like simplexml_load_file(), URL-decode the filename passed to them. If that filename contains URL-encoded NUL character, this may cause the function to interpret this as the end of the filename, thus interpreting the filename differently from what the user intended, which may lead it to reading a different file than intended.

Weakness

The product does not properly filter, remove, quote, or otherwise manage the invalid use of special elements in user-controlled input, which could cause adverse effect on its behavior and integrity.

Affected Software

Name Vendor Start Version End Version
Php Php 7.3.0 (including) 7.3.33 (excluding)
Php Php 7.4.0 (including) 7.4.26 (excluding)
Php Php 8.0.0 (including) 8.0.13 (excluding)
Red Hat Enterprise Linux 8 RedHat php:7.4-8070020220707122009.afd00e68 *
Red Hat Software Collections for Red Hat Enterprise Linux 7 RedHat rh-php73-php-0:7.3.33-1.el7 *
Php5 Ubuntu esm-infra-legacy/trusty *
Php5 Ubuntu trusty *
Php5 Ubuntu trusty/esm *
Php7.0 Ubuntu esm-infra/xenial *
Php7.0 Ubuntu upstream *
Php7.0 Ubuntu xenial *
Php7.2 Ubuntu bionic *
Php7.4 Ubuntu focal *
Php7.4 Ubuntu hirsute *
Php7.4 Ubuntu upstream *
Php8.0 Ubuntu impish *
Php8.0 Ubuntu upstream *

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