Title: Windows_Command_Injection Vulnerability on POST:/api/v1/savings-transaction
Project: Sanity 7th July
Description:
Assertion
Name: Windows Injection ( 1 )
Overview: Windows Injection is an attack in which the attacker is able to execute OS commands on the hosting server via vulnerable application. In this attack, the attacker-supplied operating system commands are usually executed with the privileges of the vulnerable application.
Severity: Command Injection is classified under the category of “Injection Attacks” by OWASP. “Injection Attacks” is ranked at 8th position in 2019 OWASP API Top 10 ( 2 ) and consistently rated at Top 1 Category of Attack by OWASP in years 2010, 2013 and 2017 ( 3 ). Command Injection is rated at 11th position in the CWE / SANS Top 25 ( 4 ).
Vulnerability Impact: Command injection is treated under the “Attack” category, in which the attacker extends the default functionality of the application, which executes system commands.
Upload of malicious program or even obtain password
Fully compromise the hosting application
Can compromise other parts of hosting infrastructure exploiting trust relationship
Exploitation: Command Injection vulnerabilities typically occur when
Data enters the application from an untrusted source.
The data is part of a string that is executed as a command by the application.
By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.
Remediation: Strong input validation must be performed for user supplied input ( 5 ). Also follow the input validation cheat sheet from OWASP
Use an "accept known good" input validation strategy. Reject input not strictly conforming to specifications
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
Do not rely exclusively on looking for malicious or malformed inputs
Title: Windows_Command_Injection Vulnerability on POST:/api/v1/savings-transaction Project: Sanity 7th July Description:
Assertion Name: Windows Injection ( 1 )
Overview: Windows Injection is an attack in which the attacker is able to execute OS commands on the hosting server via vulnerable application. In this attack, the attacker-supplied operating system commands are usually executed with the privileges of the vulnerable application.
Severity: Command Injection is classified under the category of “Injection Attacks” by OWASP. “Injection Attacks” is ranked at 8th position in 2019 OWASP API Top 10 ( 2 ) and consistently rated at Top 1 Category of Attack by OWASP in years 2010, 2013 and 2017 ( 3 ). Command Injection is rated at 11th position in the CWE / SANS Top 25 ( 4 ).
Vulnerability Impact: Command injection is treated under the “Attack” category, in which the attacker extends the default functionality of the application, which executes system commands.
- Upload of malicious program or even obtain password
- Fully compromise the hosting application
- Can compromise other parts of hosting infrastructure exploiting trust relationship
Exploitation: Command Injection vulnerabilities typically occur when- Data enters the application from an untrusted source.
- The data is part of a string that is executed as a command by the application.
- By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.
Remediation: Strong input validation must be performed for user supplied input ( 5 ). Also follow the input validation cheat sheet from OWASP- Use an "accept known good" input validation strategy. Reject input not strictly conforming to specifications
- 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
- Do not rely exclusively on looking for malicious or malformed inputs
References:Risk: Windows_Command_Injection Severity: Critical API Endpoint: http://95.217.118.53:8080/api/v1/savings-transaction Environment: Master Playbook: ApiV1SavingsTransactionPostBodyParamWindowsCommandInjection Researcher: [apisec Bot]
QUICK TIPS
Suggestion: Effort Estimate: null Hrs Wire Logs:
IMPORTANT LINKS
Vulnerability Details: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/dashboard/8a8094a07b731c32017b75a083613901/details
Project: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/allScans
Environment: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/environments/8a8093567a8012b6017a803bf3181500/edit
Scan Dashboard: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/profiles/8a8093567a8012b6017a803c070d16cb/runs/8a8094a07b731c32017b759b22d233cb
Playbook: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/playbooks/ApiV1SavingsTransactionPostBodyParamWindowsCommandInjection
Coverage: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/categories
Code Sample: https://cloud.fxlabs.io/#/app/projects/8a8093567a8012b6017a803bf31114fd/dashboard/8a8094a07b731c32017b75a083613901/codesamples
PS: Please contact support@apisec.ai for apisec access and login issues.
--- apisec Bot ---