drupal drupal CVE-2020-28949 vulnerability in Drupal and Other Products
Published on November 19, 2020

product logo product logo product logo product logo
Archive_Tar through 1.4.10 has :// filename sanitization only to address phar attacks, and thus any other stream-wrapper attack (such as file:// to overwrite files) can still succeed.

NVD

Known Exploited Vulnerability

This PEAR Archive_Tar Deserialization of Untrusted Data Vulnerability is part of CISA's list of Known Exploited Vulnerabilities. PEAR Archive_Tar allows an unserialization attack because phar: is blocked but PHAR: is not blocked. PEAR stands for PHP Extension and Application Repository and it is an open-source framework and distribution system for reusable PHP components with known usage in third-party products such as Drupal Core and Red Hat Linux.

The following remediation steps are recommended / required by September 15, 2022: Apply updates per vendor instructions.

Vulnerability Analysis

CVE-2020-28949 can be exploited with local system access, requires user interaction. This vulnerability is considered to have a low attack complexity. It has an exploitability score of 1.8 out of four. The potential impact of an exploit of this vulnerability is considered to be very high.

What is an Injection Vulnerability?

The software constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Software has certain assumptions about what constitutes data and control respectively. It is the lack of verification of these assumptions for user-controlled input that leads to injection problems. Injection problems encompass a wide variety of issues -- all mitigated in very different ways and usually attempted in order to alter the control flow of the process. For this reason, the most effective way to discuss these weaknesses is to note the distinct features which classify them as injection weaknesses. The most important issue to note is that all injection problems share one thing in common -- i.e., they allow for the injection of control plane data into the user-controlled data plane. This means that the execution of the process may be altered by sending code in through legitimate data channels, using no other mechanism. While buffer overflows, and many other flaws, involve the use of some further issue to gain execution, injection problems need only for the data to be parsed. The most classic instantiations of this category of weakness are SQL injection and format string vulnerabilities.

CVE-2020-28949 has been classified to as an Injection vulnerability or weakness.


Products Associated with CVE-2020-28949

You can be notified by stack.watch whenever vulnerabilities like CVE-2020-28949 are published in these products:

 
 
 
 

What versions are vulnerable to CVE-2020-28949?