CVE-2025-68273: Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints

Published Jan 1, 2026
·
Updated

[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: 1. Missing Protection: The tokensecurity.js file defines an array of paths that require authentication. However, the following paths defined in src/serverroutes.ts are missing from this list: - /skServer/serialports - /skServer/availablePaths - /skServer/hasAnalyzer

2. Unrestricted Access: Because they are missing from the protection list, the httpauthorize middleware allows access to these paths even when enableSecurity is set to true.

Exploit Scenario: 1. Reconnaissance: An attacker scans the server for these endpoints. 2. Data Extraction: - Querying /skServer/availablePaths returns 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/serialports reveals connected hardware (e.g., /dev/ttyUSB0), aiding in physical device targeting.

PoC The following Python script demonstrates the vulnerability by querying the exposed endpoints without any authentication headers.

python import urllib.request import json

BASEURL = "http://localhost:3000"

def checkendpoint(name, path): url = f"{BASEURL}{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 ---") checkendpoint("Serial Ports", "/skServer/serialports") checkendpoint("Available Paths", "/skServer/availablePaths") checkendpoint("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: 1. Full Data Schema: The /skServer/availablePaths endpoint 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. 2. Hardware Configuration: The /skServer/serialports endpoint exposed the list of connected serial devices. 3. System Capabilities: The /skServer/hasAnalyzer endpoint 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.

javascript // 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}, httpauthorize(false)) )

Other sources

Signal K Server is a server application that runs on a central hub in a boat. An unauthenticated information disclosure vulnerability in versions prior to 2.19.0 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. Version 2.19.0 patches the issue.

— MITRE

Affected Software

3 affected componentsFixes available
Signal K Signal K Server<2.19.0
npm/signalk-server<2.19.0
2.19.0
SignalK Signal K Server<2.19.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/signalk-server to a version that resolves this vulnerability.

    Fixed in 2.19.0
  2. Upgrade

    Upgrade Signal K Server to a version that resolves this vulnerability.

    Fixed in 2.19.0
  3. Configuration

    Add /skServer/availablePaths, /skServer/hasAnalyzer, and /skServer/serialports to the authentication-protected paths list in src/tokensecurity.js.

    Signal K Server protected routes in src/tokensecurity.js = /skServer/availablePaths, /skServer/hasAnalyzer, /skServer/serialports

Event History

Jan 1, 2026
CVE Published
via MITRE·06:21 PM
Data Sourced
via MITRE·06:21 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Jan 2, 2026
Advisory Published
via GitHub·03:22 PM
Data Sourced
via GitHub·03:22 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-68273?

CVE-2025-68273 is classified as a medium severity vulnerability due to its potential for unauthorized access to sensitive system information.

2

How do I fix CVE-2025-68273?

To fix CVE-2025-68273, upgrade your Signal K Server to version 2.19.0 or later.

3

What type of vulnerability is CVE-2025-68273?

CVE-2025-68273 is an unauthenticated information disclosure vulnerability.

4

What information can be disclosed by CVE-2025-68273?

CVE-2025-68273 allows unauthorized users to retrieve sensitive system information, including the SignalK data schema and connected serial devices.

5

Which versions of Signal K Server are affected by CVE-2025-68273?

Versions of Signal K Server prior to 2.19.0 are affected by CVE-2025-68273.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203