Home / Vulnerability Database / T-SQL : Command injection (job)
T-SQL
T-SQL : Command injection (job)
Classification
OWASP Top 10 2013
OWASP Top 10 2017
OWASP Top 10 2021
OWASP ASVS
PCI DSS 4.0
CWE/SANS Top 25 2011
Overview
The application uses a function for job management using arguments that may have originated from an untrusted source. An adversary can alter the parameters of the job.
Executing commands obtained from data from an untrusted source is insecure.
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.
References
- OWASP Top 10 2017-A1-Injection
- OWASP Top 10 2013-A1-Injection
- DBMS_SCHEDULER - docs.oracle.com
- Executing operation system commands from PL/SQL: an Oracle White Paper (pdf)
- CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
- CWE CATEGORY: OWASP Top Ten 2017 Category A1 - Injection
MEDIUM
DerScanner Severity Score
Do you want to fix T-SQL : Command injection (job) in your application?
See also
T-SQL
T-SQL : Weak encryption algorithm
T-SQL
T-SQL : Weak hashing algorithm
T-SQL
