CVE-2025-68273

5.3 MEDIUM

📋 TL;DR

Signal K Server versions before 2.19.0 have an unauthenticated information disclosure vulnerability that allows any user to retrieve sensitive system information including the full data schema, connected serial devices, and installed analyzer tools. This affects boat owners and operators using Signal K Server as their central marine data hub. The exposed information facilitates reconnaissance for potential follow-up attacks.

💻 Affected Systems

Products:
  • Signal K Server
Versions: All versions prior to 2.19.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all Signal K Server deployments regardless of configuration. The vulnerability is present in the default installation.

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers gain detailed knowledge of the vessel's systems, connected devices, and data structure, enabling targeted attacks that could compromise navigation systems, engine controls, or safety equipment.

🟠

Likely Case

Unauthorized users map the vessel's digital infrastructure, identify vulnerable components, and plan subsequent attacks based on the exposed system architecture.

🟢

If Mitigated

Limited exposure of non-critical information with no direct system compromise, though some reconnaissance data may still be available to attackers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability requires no authentication and minimal technical skill to exploit. Attackers can simply query the vulnerable endpoint to retrieve sensitive information.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.19.0

Vendor Advisory: https://github.com/SignalK/signalk-server/security/advisories/GHSA-fpf5-w967-rr2m

Restart Required: Yes

Instructions:

1. Backup current configuration and data. 2. Stop the Signal K Server service. 3. Update to version 2.19.0 using your package manager or manual installation. 4. Restart the Signal K Server service. 5. Verify the update was successful.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict network access to Signal K Server to only trusted networks and devices

iptables -A INPUT -p tcp --dport 3000 -s TRUSTED_IP -j ACCEPT
iptables -A INPUT -p tcp --dport 3000 -j DROP

Reverse Proxy with Authentication

all

Place Signal K Server behind a reverse proxy that requires authentication

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Signal K Server from untrusted networks
  • Deploy a web application firewall (WAF) or reverse proxy with authentication in front of Signal K Server

🔍 How to Verify

Check if Vulnerable:

Check if unauthenticated requests to Signal K Server endpoints return sensitive system information that should be protected

Check Version:

signalk-server --version

Verify Fix Applied:

After updating to 2.19.0, verify that unauthenticated requests no longer return sensitive system information

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to system information endpoints
  • Multiple failed authentication attempts followed by information requests

Network Indicators:

  • Unusual traffic to Signal K Server from external IP addresses
  • Repeated requests to system information endpoints

SIEM Query:

source="signalk-server" AND (uri_path="/signalk/v1/api/" OR uri_path CONTAINS "/system/") AND http_status=200 AND user="anonymous"

🔗 References

📤 Share & Export