CVE-2025-68273: Signalk server Signal K Server Vulnerable To Vulnerability

MODERATE
Advisory Identifier: GHSA-fpf5-w967-rr2m
CVSS 5.3
CWE-200
Published
Advisory Summary

CVE-2025-68273 is a MODERATE (CVSS 5.3) signal k server vulnerable to vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Signalk server libraries in the npm ecosystem. The issue involves signal k server vulnerable to unauthenticated information disclosure via exposed endpoints. Remediation is available by upgrading affected packages to version 2.19.0.

CVE-2025-68273 at a Glance

CVE Identifier CVE-2025-68273
GHSA Identifier GHSA-fpf5-w967-rr2m
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Signalk server
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-68273

To remediate this vulnerability, upgrade all affected Signalk server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

signalk-server fixed: 2.19.0
npm install signalk-server@2.19.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls signalk-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-68273, inspect your project dependencies using npm:

npm ls signalk-server

Analyze the terminal output to locate any version of Signalk server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.19.0), your application is affected.

Note: The npm ls signalk-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Signalk server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

[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 `http_authorize` 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 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: 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}`, http_authorize(false)) ) ```

CVE-2025-68273 Affected Signalk server Versions

1 component(s)
Fixed Versions:
2.19.0
Product / Package Ecosystem Affected Versions Fixed Version
signalk-server
npm
< 2.19.0
2.19.0

References

Frequently Asked Questions

What is CVE-2025-68273?
CVE-2025-68273 is a security vulnerability in Signalk server involving Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Signalk server versions are affected?
Affected versions include releases prior to 2.19.0 across affected packages: signalk-server.
What version fixes CVE-2025-68273?
Upgrading to 2.19.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is signalk-server affected?
Yes, signalk-server is affected in releases prior to 2.19.0. Upgrade your dependency to 2.19.0 or later.
What is the CVSS score of CVE-2025-68273?
CVE-2025-68273 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2025-68273?
CVE-2025-68273 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2025-68273?
Run the dependency tree command: 'npm ls signalk-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fpf5-w967-rr2m",
  "modified" : "2026-01-02T15:22:11Z",
  "published" : "2026-01-02T15:22:11Z",
  "aliases" : [ "CVE-2025-68273" ],
  "summary" : "Signal K Server Vulnerable to Unauthenticated Information Disclosure via Exposed Endpoints",
  "details" : "[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.\n\n### Summary\nAn 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.\n\n### Details\nThe vulnerability stems from the fact that several sensitive API endpoints are not included in the authentication middleware's protection list in `src/tokensecurity.js`.\n\n**Vulnerable Code Analysis:**\n1.  **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:\n    - `/skServer/serialports`\n    - `/skServer/availablePaths`\n    - `/skServer/hasAnalyzer`\n\n2.  **Unrestricted Access**: Because they are missing from the protection list, the `http_authorize` middleware allows access to these paths even when `enableSecurity` is set to `true`.\n\n**Exploit Scenario:**\n1.  **Reconnaissance**: An attacker scans the server for these endpoints.\n2.  **Data Extraction**:\n    - 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.\n    - Querying `/skServer/serialports` reveals connected hardware (e.g., `/dev/ttyUSB0`), aiding in physical device targeting.\n\n### PoC\nThe following Python script demonstrates the vulnerability by querying the exposed endpoints without any authentication headers.\n\n```python\nimport urllib.request\nimport json\n\nBASE_URL = \"http://localhost:3000\"\n\ndef check_endpoint(name, path):\n    url = f\"{BASE_URL}{path}\"\n    print(f\"[*] Checking {name} at {url}...\")\n    try:\n        req = urllib.request.Request(url)\n        with urllib.request.urlopen(req) as response:\n            if response.getcode() == 200:\n                print(f\"[!] VULNERABLE: {name} is accessible without authentication!\")\n                content = response.read().decode('utf-8')\n                print(f\"    Snippet: {content[:100]}...\")\n            else:\n                print(f\"[-] Secure: {response.getcode()}\")\n    except urllib.error.HTTPError as e:\n        print(f\"[-] Secure: {e.code}\")\n    except Exception as e:\n        print(f\"[-] Error: {e}\")\n\nif __name__ == \"__main__\":\n    print(\"--- SignalK Information Disclosure PoC ---\")\n    check_endpoint(\"Serial Ports\", \"/skServer/serialports\")\n    check_endpoint(\"Available Paths\", \"/skServer/availablePaths\")\n    check_endpoint(\"Analyzer Check\", \"/skServer/hasAnalyzer\")\n```\n\n**Expected Result:**\nThe script will output `[!] VULNERABLE` for all three endpoints, showing snippets of the leaked JSON data.\n\n### Impact\n**Verified Information Disclosure**:\nDuring our verification, we successfully retrieved the following sensitive information without any authentication:\n1.  **Full Data Schema**: The `/skServer/availablePaths` endpoint returned the complete JSON schema of the vessel's data.\n    *   **Example**: `environment.sun.sunrise`, `navigation.position`\n    *   **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.\n2.  **Hardware Configuration**: The `/skServer/serialports` endpoint exposed the list of connected serial devices.\n3.  **System Capabilities**: The `/skServer/hasAnalyzer` endpoint revealed whether traffic analysis tools were installed.\n\nThis information allows an attacker to map the system's internal state and capabilities, significantly facilitating further targeted attacks (Reconnaissance).\n\n---\n### Remediation\n**Update `src/tokensecurity.js`**\nAdd the missing paths to the list of protected routes in `src/tokensecurity.js`.\n\n```javascript\n// src/tokensecurity.js\n\n// ... existing protected paths ...\n;[\n  '/apps',\n  '/appstore',\n  '/plugins',\n  '/restart',\n  '/runDiscovery',\n  '/security',\n  '/vessel',\n  '/providers',\n  '/settings',\n  '/webapps',\n  '/skServer/inputTest',\n  // ADD THESE LINES:\n  '/skServer/serialports',\n  '/skServer/availablePaths',\n  '/skServer/hasAnalyzer'\n].forEach((p) =>\n  app.use(`${SERVERROUTESPREFIX}${p}`, http_authorize(false))\n)\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "signalk-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.19.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/SignalK/signalk-server/security/advisories/GHSA-fpf5-w967-rr2m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-68273"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/SignalK/signalk-server/commit/ead2a03d8994969cafcca0320abee16f0e66e7a9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/SignalK/signalk-server"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/SignalK/signalk-server/releases/tag/v2.19.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-02T15:22:11Z",
    "nvd_published_at" : "2026-01-01T19:15:53Z"
  }
}