Normal content
``` ### 2. Create a bookmark via the API ```bash curl -X POST http://localhost:3000/api/v1/bookmarks \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"type": "link", "url": "https://attacker.example.com/ssrf.html"}' ``` ### 3. Result The main URL (`https://attacker.example.com/ssrf.html`) passes `validateUrl()` since it resolves to a public IP. After the HTML is fetched, `metascraper-logo-favicon` extracts the favicon URLs and calls `reachable-url`/`got` to verify them. The server makes HTTP GET requests to: - `http://169.254.169.254/latest/meta-data/` (AWS IMDS) - `http://127.0.0.1:3000/api/v1/users/whoami` (localhost) - `http://192.168.1.1/admin` (internal network) These requests bypass all SSRF protections. Verification: Monitor outbound network traffic from the karakeep container or check the logo field in the bookmark response. ## Impact - **Cloud metadata access**: On AWS/GCP/Azure deployments, the server can be forced to fetch instance metadata (e.g., `http://169.254.169.254/latest/meta-data/iam/security-credentials/`) which may expose IAM credentials. - **Internal service discovery**: Attacker can probe internal network services and ports by checking whether the favicon URL was reachable. - **Redirect-based data leak**: If an internal service responds with a redirect, the final URL (potentially containing tokens or session data) is stored as the bookmark's logo field and visible to the attacker. - **Bypass of explicit security controls**: The application's SSRF protections (IP blacklist, DNS resolution, redirect validation) are rendered ineffective for this code path. ## Suggested Fix ```diff // apps/workers/scripts/parseHtmlSubprocess.ts + import { validateUrl } from "network"; + + // Create a got hook that validates URLs before requests + const ssrfHook = { + beforeRequest: [ + async (options) => { + const result = await validateUrl(options.url.toString(), false); + if (!result.ok) { + throw new Error(`SSRF blocked: ${result.reason}`); + } + } + ] + }; + metascraperLogo({ gotOpts: { + hooks: ssrfHook, agent: { ... }, }, }), ``` Alternatively, run the parse subprocess in a network-restricted sandbox (network namespace, nsjail, or a Docker container with restricted networking). ## Which versions are affected by GHSA-7rx4-c5vx-g8w3? 2 open source packages ship an affected version, including @karakeep/sdk. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@karakeep/sdk` | npm | All versions | 0.32.0 | | `@karakeep/sdk` | npm | All versions | 0.32.0 | ## How do I fix GHSA-7rx4-c5vx-g8w3? Upgrade @karakeep/sdk to 0.32.0 or later. ## Is GHSA-7rx4-c5vx-g8w3 being exploited? There is no known exploitation of GHSA-7rx4-c5vx-g8w3 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-7rx4-c5vx-g8w3 and fix it if it is affected. What it is: GHSA-7rx4-c5vx-g8w3 is a server-side request forgery vulnerability in @karakeep/sdk, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of GHSA-7rx4-c5vx-g8w3 in the wild and no public exploit code. Affected packages and fixed versions: - @karakeep/sdk (npm): affected all versions; fixed in 0.32.0 - @karakeep/sdk (npm): affected all versions; fixed in 0.32.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-7rx4-c5vx-g8w3/ (Markdown: https://insights.sbomify.com/GHSA-7rx4-c5vx-g8w3/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-7rx4-c5vx-g8w3 --- From sbomify Insights: https://insights.sbomify.com/GHSA-7rx4-c5vx-g8w3/ Summaries are generated and may contain mistakes; the official description above is the record.