Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints
[Note] This is a separate issue from the RCE vulnerability (State Pollution) currently being patched. While related to tokensecurity.js, it involves different endpoints and risks.
Summary
An unauthenticated information disclosure vulnerability allows any user to retrieve sensitive system information, including the full SignalK data schema, connected serial devices, and installed analyzer tools. This exposure facilitates reconnaissance for further attacks.
Details
The vulnerability stems from the fact that several sensitive API endpoints are not included in the authentication middleware's protection list in src/tokensecurity.js.
Vulnerable Code Analysis:
-
Missing Protection: The
tokensecurity.jsfile defines an array of paths that require authentication. However, the following paths defined insrc/serverroutes.tsare missing from this list:/skServer/serialports/skServer/availablePaths/skServer/hasAnalyzer
-
Unrestricted Access: Because they are missing from the protection list, the
http_authorizemiddleware allows access to these paths even whenenableSecurityis set totrue.
Exploit Scenario:
- Reconnaissance: An attacker scans the server for these endpoints.
- Data Extraction:
- Querying
/skServer/availablePathsreturns the full JSON schema of the vessel's data (e.g.,environment.sun.sunrise,navigation.position), allowing the attacker to know exactly what data points are available for targeting. - Querying
/skServer/serialportsreveals connected hardware (e.g.,/dev/ttyUSB0), aiding in physical device targeting.
- Querying
PoC
The following Python script demonstrates the vulnerability by querying the exposed endpoints without any authentication headers.
import urllib.request
import json
BASE_URL = "http://localhost:3000"
def check_endpoint(name, path):
url = f"{BASE_URL}{path}"
print(f"[*] Checking {name} at {url}...")
try:
req = urllib.request.Request(url)
with urllib.request.urlopen(req) as response:
if response.getcode() == 200:
print(f"[!] VULNERABLE: {name} is accessible without authentication!")
content = response.read().decode('utf-8')
print(f" Snippet: {content[:100]}...")
else:
print(f"[-] Secure: {response.getcode()}")
except urllib.error.HTTPError as e:
print(f"[-] Secure: {e.code}")
except Exception as e:
print(f"[-] Error: {e}")
if __name__ == "__main__":
print("--- SignalK Information Disclosure PoC ---")
check_endpoint("Serial Ports", "/skServer/serialports")
check_endpoint("Available Paths", "/skServer/availablePaths")
check_endpoint("Analyzer Check", "/skServer/hasAnalyzer")
Expected Result:
The script will output [!] VULNERABLE for all three endpoints, showing snippets of the leaked JSON data.
Impact
Verified Information Disclosure: During our verification, we successfully retrieved the following sensitive information without any authentication:
- Full Data Schema: The
/skServer/availablePathsendpoint returned the complete JSON schema of the vessel's data.- Example:
environment.sun.sunrise,navigation.position - Leakage of Internal State: We also observed entries like
notifications.security.accessRequest.readwrite.attacker-device-32, which revealed the presence and IDs of pending access requests (traces of our DoS attack), showing that internal server state is exposed.
- Example:
- Hardware Configuration: The
/skServer/serialportsendpoint exposed the list of connected serial devices. - System Capabilities: The
/skServer/hasAnalyzerendpoint revealed whether traffic analysis tools were installed.
This information allows an attacker to map the system's internal state and capabilities, significantly facilitating further targeted attacks (Reconnaissance).
Remediation
Update src/tokensecurity.js
Add the missing paths to the list of protected routes in src/tokensecurity.js.
// src/tokensecurity.js
// ... existing protected paths ...
;[
'/apps',
'/appstore',
'/plugins',
'/restart',
'/runDiscovery',
'/security',
'/vessel',
'/providers',
'/settings',
'/webapps',
'/skServer/inputTest',
// ADD THESE LINES:
'/skServer/serialports',
'/skServer/availablePaths',
'/skServer/hasAnalyzer'
].forEach((p) =>
app.use(`${SERVERROUTESPREFIX}${p}`, http_authorize(false))
)
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| npm-Paket | signalk-server | < 2.19.0 | 2.19.0 |
Verweise
- https://github.com/SignalK/signalk-server/security/advisories/GHSA-fpf5-w967-rr2m
- https://nvd.nist.gov/vuln/detail/CVE-2025-68273
- https://github.com/SignalK/signalk-server/commit/ead2a03d8994969cafcca0320abee16f0e66e7a9
- https://github.com/SignalK/signalk-server
- https://github.com/SignalK/signalk-server/releases/tag/v2.19.0
- CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Schwäche (CWE)
CWE-200- Plattform
- npm
- Paket
signalk-server- Veröffentlicht
- 02.01.2026
- Aktualisiert
- 11.10.2026 10:22
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-fpf5-w967-rr2m - CC BY 4.0
Schwachstellenhistorie: signalk-server
Alle veröffentlichten Schwachstellen dieses Pakets (npm-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 14
- Erste → letzte
- 01.2026 06.2026
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 0
Verteilung nach Schweregrad
- Kritisch 3
- Hoch 4
- Mittel 6
- Niedrig 1
Veröffentlichungen pro Jahr
- 2026: 14
-
Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.