https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 01:17:43 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-264787 EUVD-2026-264787 https://cve.radiocsirt.org/vuln/euvd-2026-264787 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68273 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68273 https://cve.radiocsirt.org/vuln/ghsa-fpf5-w967-rr2m <p><strong>Affected:</strong> npm: signalk-server</p> <p>[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.</p> <p>### 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.</p> <p>### Details The vulnerability stems from the fact that several sensitive API endpoints are not included in the authentication middleware&#39;s protection list in `src/tokensecurity.js`.</p> <p>**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`</p> <p>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`.</p> <p>**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&#39;s data (e.g., `environment.sun.sunrise`, `navigation.position`), allowing the attacker to know exactly what data points are availabl…</p> <p><strong>Affected:</strong> npm: signalk-server</p> <p>[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.</p> <p>### 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.</p> <p>### Details The vulnerability stems from the fact that several sensitive API endpoints are not included in the authentication middleware&#39;s protection list in `src/tokensecurity.js`.</p> <p>**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`</p> <p>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`.</p> <p>**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&#39;s data (e.g., `environment.sun.sunrise`, `navigation.position`), allowing the attacker to know exactly what data points are availabl…</p> https://cve.radiocsirt.org/vuln/ghsa-fpf5-w967-rr2m