Spug through 3.4.0 Remote Code Execution via ping_check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| openspug | spug | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Openspug | Spug |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.3% (1.318% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openspug
Openspug spug |
|
| Vendors & Products |
Openspug
Openspug spug |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Spug through 3.4.0 Remote Code Execution via ping_check | |
| Weaknesses | CWE-78 | |
| References |
|
|
| Metrics |
cvssV3_1
|