Spug through 3.4.0 Remote Code Execution via ping_check
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 1.3%
exploitation probability
1.3%top 30% of all CVEs
observed exploitation
nono source reports it
Spug through 3.4.0 contains a remote code execution vulnerability in the ping_check function that interpolates user-supplied monitor addresses directly into shell commands without validation. Authenticated users with monitor permissions can inject shell metacharacters via the /monitor/run_test/ endpoint to execute arbitrary commands as the Spug process user.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
openspug · spugReferences
https://github.com/openspug/spughttps://github.com/openspug/spug/blob/v3.4.0/spug_api/apps/monitor/executors.pyhttps://github.com/openspug/spug/blob/v3.4.0/spug_api/apps/monitor/views.pyhttps://github.com/openspug/spug/commit/97aebf133e1f9cbb35ccebadab1faedfdfe93f42https://github.com/openspug/spug/issues/741https://www.vulncheck.com/advisories/spug-through-3.4.0-remote-code-execution-via-ping-check