GHSA-gfmv-vh34-h2x5
HIGHGHSA-gfmv-vh34-h2x5 is a high-severity (CVSS 7.5) CWE-284 vulnerability in signalk-server. O3 Security confirms whether GHSA-gfmv-vh34-h2x5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Signal K Server: Unauthenticated Source Priorities Manipulation
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
signalk-servernpmDescription
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | signalk-server | all versions | 2.24.0-beta.1 |
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.24.0-beta.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gfmv-vh34-h2x5 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-gfmv-vh34-h2x5 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-gfmv-vh34-h2x5. 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-gfmv-vh34-h2x5 in your dependencies?
O3 detects GHSA-gfmv-vh34-h2x5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.