Summary
signalk-server has SSRF via absolute signalk.appIcon URL in the app store icon fetcher
The app store icon code (dist/appstore/icon-probe.js around line 200 and icon-bytes.js around line 138) resolves a plugin's declared signalk.appIcon. Relative paths are pinned to the CDN, but an absolute http(s) URL is used as-is: the server fetches it, follows redirects, and stores any image/* response as the plugin's icon, which is then served to the admin UI. Unrelated to GHSA-q59x-jc9f-gfqf.
Affected
signalk-server 2.33.0 (latest).
Reproduction
The real dist modules driven directly, Docker with --network none; a local "internal" service on 127.0.0.1 logs requests:
[CONTROL relative] declared=../../icon.png
resolved=null
internal-service hits: [] stored: null
[ATTACK absolute] declared=http://127.0.0.1:35013/latest/meta-data/iam
resolved=http://127.0.0.1:35013/latest/meta-data/iam
internal-service hits: ["GET /latest/meta-data/iam"] stored: .../icon-bytes/[email protected] (70 bytes)
[ATTACK redirect] declared=http://127.0.0.1:35013/redir
internal-service hits: ["GET /redir","GET /internal-secret-via-redirect.png"] stored: .../icon-bytes/[email protected] (70 bytes)
The modules were tested directly rather than through a full running server.
Impact
Anyone who can get a plugin listed in the app store (publishing an npm package with the signalk keywords) can make every signalk-server that browses the app store send requests to internal addresses on the vessel network and to cloud metadata endpoints. Responses with an image content type are stored and served back to the user.
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
GHSA-7WPF-CH8F-5F4X has a CVSS score of 4.2 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.34.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Only accept relative icon paths resolved against the CDN (or an https allowlist of known hosts), do not follow redirects to other hosts, and reject private, loopback and link-local addresses after resolution.
Frequently Asked Questions
- What is GHSA-7WPF-CH8F-5F4X? GHSA-7WPF-CH8F-5F4X is a medium-severity server-side request forgery (SSRF) vulnerability in signalk-server (npm), affecting versions >= 2.28.0-beta.2, < 2.34.0. It is fixed in 2.34.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- How severe is GHSA-7WPF-CH8F-5F4X? GHSA-7WPF-CH8F-5F4X has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of signalk-server are affected by GHSA-7WPF-CH8F-5F4X? signalk-server (npm) versions >= 2.28.0-beta.2, < 2.34.0 is affected.
- Is there a fix for GHSA-7WPF-CH8F-5F4X? Yes. GHSA-7WPF-CH8F-5F4X is fixed in 2.34.0. Upgrade to this version or later.
- Is GHSA-7WPF-CH8F-5F4X exploitable, and should I be worried? Whether GHSA-7WPF-CH8F-5F4X is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-7WPF-CH8F-5F4X is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-7WPF-CH8F-5F4X? Upgrade
signalk-serverto 2.34.0 or later.