UpSnap - Unauthenticated Initial-Superuser Takeover Chains to Root RCE via wake_cmd
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| seriousm4x | UpSnap | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Seriousm4x | Upsnap |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.080% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Seriousm4x
Seriousm4x upsnap |
|
| Vendors & Products |
Seriousm4x
Seriousm4x upsnap |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | UpSnap is a wake on lan web app. Versions 4.4.1 through 5.3.5 are vulnerable to a missing-authentication / privilege-escalation chain in `pb.HandlerInitSuperuser` (`backend/pb/handlers.go:249`), reachable as `POST /api/upsnap/init-superuser`. The vulnerable code lacks any authentication, setup token, IP allow-list, or rate limit and is gated only by a `totalSuperusers > 0` count check — a condition that is false on every fresh install — allowing an unauthenticated network-adjacent attacker to register the initial superuser account, receive a long-lived JWT, and pivot to root remote code execution at `backend/networking/wake.go:43` (`exec.CommandContext(ctx, "/bin/sh", "-c", wake_cmd)`). Version 5.4.0 fixes the issue. | |
| Title | UpSnap - Unauthenticated Initial-Superuser Takeover Chains to Root RCE via wake_cmd | |
| Weaknesses | CWE-269 CWE-306 CWE-78 CWE-862 |
|
| References |
| |
| Metrics |
cvssV3_1
|