# CVE-2024-41664: Blind SSRF via Canarytoken Webhook

> Attackers can exploit a blind SSRF in the webhook feature to map internal network ports and access internal resources.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-41664?

CVE-2024-41664 is a medium-severity server-side request forgery vulnerability in thinkst canarytokens, published on 23 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Canarytokens help track activity and actions on a network. Prior to `sha-8ea5315`, Canarytokens.org was vulnerable to a blind SSRF in the Webhook alert feature. When a Canarytoken is created, users choose to receive alerts either via email or via a webhook. If a webhook is supplied when a  Canarytoken is first created, the site will make a test request to the supplied URL to ensure it accepts alert notification HTTP requests. No safety checks were performed on the URL, leading to a Server-Side Request Forgery vulnerability. The SSRF is Blind because the content of the response is not displayed to the creating user; they are simply told whether an error occurred in making the test request. Using the Blind SSRF, it was possible to map out open ports for IPs inside the Canarytokens.org infrastructure. This issue is now patched on Canarytokens.org. Users of self-hosted Canarytokens installations can update by pulling the latest Docker image, or any Docker image after `sha-097d91a`.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-41664?


## How do I fix CVE-2024-41664?

No fix has been published for CVE-2024-41664 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41664 being exploited?

There is no known exploitation of CVE-2024-41664 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41664 and fix it if it is affected.

What it is: CVE-2024-41664 is a medium-severity server-side request forgery vulnerability in thinkst canarytokens, published on 23 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41664 in the wild and no public exploit code.

Affected product: thinkst canarytokens. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2024-41664/ (Markdown: https://insights.sbomify.com/CVE-2024-41664/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41664
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41664
- OSV: https://osv.dev/vulnerability/CVE-2024-41664

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41664/
Summaries are generated and may contain mistakes; the official description above is the record.