Vulnerabilities > CVE-2021-21316 - Injection vulnerability in Less-Openui5 Project Less-Openui5

CVSS 7.8 - HIGH

Attack vector

LOCAL

Attack complexity

LOW

Privileges required

NONE

Confidentiality impact

HIGH

Integrity impact

HIGH

Availability impact

HIGH

local

low complexity

less-openui5-project

CWE-74

NVD

Published: 2021-02-16

Updated: 2021-02-26

Summary

less-openui5 is an npm package which enables building OpenUI5 themes with Less.js. In less-openui5 before version 0.10., when processing theming resources (i.e. `*.less` files) with less-openui5 that originate from an untrusted source, those resources might contain JavaScript code which will be executed in the context of the build process. While this is a feature of the Less.js library it is an unexpected behavior in the context of OpenUI5 and SAPUI5 development. Especially in the context of UI5 Tooling which relies on less-openui5. An attacker might create a library or theme-library containing a custom control or theme, hiding malicious JavaScript code in one of the .less files. Refer to the referenced GHSA-3crj-w4f5-gwh4 for examples. Starting with Less.js version 3.0.0, the Inline JavaScript feature is disabled by default. less-openui5 however currently uses a fork of Less.js v1.6.3. Note that disabling the Inline JavaScript feature in Less.js versions 1.x, still evaluates code has additional double codes around it. We decided to remove the inline JavaScript evaluation feature completely from the code of our Less.js fork. This fix is available in less-openui5 version 0.10.0.

Vulnerable Configurations

Part	Description	Count
Application	Less-Openui5_Project Less Openui5 Project Less Openui5 0.1.0 Less Openui5 Project Less Openui5 0.1.1 Less Openui5 Project Less Openui5 0.1.2 Less Openui5 Project Less Openui5 0.1.3 Less Openui5 Project Less Openui5 0.2.0 Less Openui5 Project Less Openui5 0.3.0 Less Openui5 Project Less Openui5 0.3.1 Less Openui5 Project Less Openui5 0.4.0 Less Openui5 Project Less Openui5 0.5.0 Less Openui5 Project Less Openui5 0.5.1 Less Openui5 Project Less Openui5 0.5.2 Less Openui5 Project Less Openui5 0.5.3 Less Openui5 Project Less Openui5 0.5.4 Less Openui5 Project Less Openui5 0.6.0 Less Openui5 Project Less Openui5 0.7.0 Less Openui5 Project Less Openui5 0.8.0 Less Openui5 Project Less Openui5 0.8.1 Less Openui5 Project Less Openui5 0.8.2 Less Openui5 Project Less Openui5 0.8.3 Less Openui5 Project Less Openui5 0.8.4 Less Openui5 Project Less Openui5 0.8.5 Less Openui5 Project Less Openui5 0.8.6 Less Openui5 Project Less Openui5 0.8.7 Less Openui5 Project Less Openui5 0.9.0	24

Common Weakness Enumeration (CWE)

CWE-74 - Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Common Attack Pattern Enumeration and Classification (CAPEC)

Buffer Overflow via Environment Variables
This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
Server Side Include (SSI) Injection
An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands.
Cross Site Scripting through Log Files
An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
Command Line Execution through SQL Injection
An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
Subverting Environment Variable Values
The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.

Summary

Vulnerable Configurations

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

References