Signal K Server: Buffered logs exposed to unauthenticated WebSocket clients
Summary
An unauthenticated WebSocket client can subscribe to the log path and receive buffered server logs.
WebSocket connections are intentionally permitted before authentication because login occurs over the WebSocket connection. However, the log subscription path does not enforce an authorization check.
processSubscribe handles subscriptions to the log path separately, without applying access control:
if (
Array.isArray(msg.subscribe) &&
msg.subscribe.length > 0 &&
msg.subscribe[0].path === 'log'
) {
if (!spark.logUnsubscribe) {
spark.logUnsubscribe = startServerLog(app, spark)
}
} else {
// normal subscriptions go through subscriptionmanager, which applies
// securityStrategy.filterReadDelta
}
startServerLog then replays the whole buffer to that socket:
app.logging.getLog().forEach((log) => {
spark.write({ type: 'LOG', data: log })
})
The asymmetry is inside this one file. Writes are gated by securityStrategy.shouldAllowWrite (ws.ts:961), normal delta subscriptions are filtered by securityStrategy.filterReadDelta (ws.ts:1159, the else branch of this same function), and the log branch consults neither.
An unauthenticated socket, which is legitimately open for login, can subscribe to log and receive buffered server logs.
Fix: Requires an administrator principal, before startServerLog, in the same way the other branch defers to securityStrategy. The fix was released with version 2.31.0-beta.1.
The investigated code path was reviewed at commit 26ab199. No server was run and no WebSocket frames were captured. AI assistance was used during the investigation.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | signalk-server | < 2.31.0-beta.1 | 2.31.0-beta.1 |
Referencias
- https://github.com/SignalK/signalk-server/security/advisories/GHSA-7m8x-x364-m26j
- https://github.com/SignalK/signalk-server/commit/1bee85114a4cb7403aba71632d9902792d6b4f0c
- https://github.com/SignalK/signalk-server
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0
- https://github.com/SignalK/signalk-server/releases/tag/v2.31.0-beta.1
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Debilidad (CWE)
CWE-306- Plataforma
- npm
- Paquete
signalk-server- Publicada
- 12.11.2026
- Actualizado
- 12.11.2026 21:17
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-7m8x-x364-m26j - CC BY 4.0
Historial de vulnerabilidades: signalk-server
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 17
- Primera → última
- 01.2026 11.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 4
- Alta 4
- Media 8
- Baja 1
Divulgaciones por año
- 2026: 17
-
Signal K Server: Buffered logs exposed to unauthenticated WebSocket clients esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.