Signal K Server: Unauthenticated Source Priorities Manipulation
Summary
The SignalK Server exposes an unauthenticated HTTP endpoint that allows remote attackers to modify navigation data source priorities. This endpoint, accessible via PUT /signalk/v1/api/sourcePriorities, does not enforce authentication or authorization checks and directly assigns user-controlled input to the server configuration.
As a result, attackers can influence which GPS, AIS, or other sensor data sources are trusted by the system. The changes are immediately applied and persisted to disk, allowing the manipulation to survive server restarts.
Affected Component
- File:
src/serverroutes.ts - Endpoint:
PUT /signalk/v1/api/sourcePriorities(also accessible at/skServer/sourcePriorities) - Lines: 1064-1076
- Function: Source priorities configuration handler
Vulnerable Code
// src/serverroutes.ts - Lines 1064-1076
app.put(
`${SERVERROUTESPREFIX}/sourcePriorities`,
(req: Request, res: Response) => {
app.config.settings.sourcePriorities = req.body
app.activateSourcePriorities()
writeSettingsFile(app, app.config.settings, (err: any) => {
if (err) {
res
.status(500)
.send('Unable to save to sourcePrefences in settings file')
} else {
res.json({ result: 'ok' })
}
})
}
)
Vulnerability Characteristics
Missing Authentication: The endpoint has zero authentication middleware, allowing unauthenticated access from any network-adjacent attacker.
Direct Configuration Assignment: User-supplied request body is directly assigned to app.config.settings.sourcePriorities without validation or sanitization.
Persistent Storage: Malicious configuration is written to disk via writeSettingsFile(), ensuring changes survive server restarts. Live Configuration Update: Changes take effect immediately via activateSourcePriorities(), affecting live navigation data processing.
No Input Validation: No JSON schema validation, type checking, or field allowlisting is performed on the request body.
Impact
- Navigation Data Manipulation: Attackers can modify source priorities to change which existing, active source's data is being used
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.24.0-beta.1 | 2.24.0-beta.1 |
Referencias
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- Debilidad (CWE)
CWE-284, CWE-306- Plataforma
- npm
- Paquete
signalk-server- Publicada
- 03.04.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-gfmv-vh34-h2x5 - 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
- 14
- Primera → última
- 01.2026 06.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 3
- Alta 4
- Media 6
- Baja 1
Divulgaciones por año
- 2026: 14
-
Signal K Server: Unauthenticated Source Priorities Manipulation 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.