Executing commands obtained from data from an untrusted source is insecure.

Injection vulnerabilities take the first place in the “OWASP Top 10 2017” web-application vulnerabilities ranking. Command injection vulnerabilities are divided into two categories:

An attacker modifies the command itself;
An attacker replaces the value of the environment variables, which implicitly changes the semantics of the command being executed.

In the given case, the application is prone to the vulnerability of the first type.

A possible attack scenario:

The application receives input data from an untrusted source, for example, user input.
The data obtained is used as a part of the string that defines the command.
Execution of the command gives an attacker the privileges which he did not previously possess.

Config files : Spring Framework vulnerability

DerScanner Severity Score

Do you want to fix Config files : Spring Framework vulnerability in your application?

See also