dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-41664

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Canarytokens.org had a blind Server-Side Request Forgery (SSRF) vulnerability in its webhook alert feature. When users created a Canarytoken with a webhook URL, the system made a test request to validate the webhook without performing any safety checks on the URL. This allowed attackers to supply internal URLs or private network IPs, enabling port scanning and internal infrastructure mapping. The vulnerability is 'blind' because only HTTP error status was returned to the user, not the response content.

MitigationUpgrade to the patched Docker image (sha-097d91a or later for self-hosted deployments). For canarytokens.org users, no action is required as the vendor has already applied the patch. Review server logs for signs of exploitation targeting internal infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify deployment type
    Determine if you are using the self-hosted Canarytokens Docker deployment or the managed canarytokens.org service. Self-hosted deployments will have your own Docker infrastructure and configuration files.
    Affected if Only self-hosted deployments are affected; managed canarytokens.org users are protected by the vendor patch.
  2. Check Docker image version for self-hosted
    Run 'docker images' or inspect your docker-compose file to identify the Canarytokens image SHA or tag. Compare against the patched version sha-097d91a.
    Affected if Using a self-hosted image with SHA older than sha-097d91a means the vulnerability is present.
  3. Verify webhook configuration exists
    Review your Canarytokens configuration files (typically config.py or environment variables) for any webhook URL settings, or check the database for created tokens with webhook alert URLs configured.
    Affected if Webhooks must be enabled and at least one token configured with a webhook URL for the SSRF to be exploitable.
  4. Audit logs for internal network access
    Search server access and error logs for HTTP requests to private IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x), localhost (127.0.0.1), or internal hostnames that originate from the webhook validation endpoint.
    Affected if Log evidence of requests to internal/private network addresses from the webhook feature indicates exploitation.

You are affected if you run a self-hosted Canarytokens deployment with a Docker image version prior to sha-097d91a and have the webhook alert feature enabled with configured webhook URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the patched Docker image (sha-097d91a or later for self-hosted deployments). For canarytokens.org users, no action is required as the vendor has already applied the patch. Review server logs for signs of exploitation targeting internal infrastructure.

Recommended fix High confidence

Docker image after sha-097d91a (or latest)

  1. Pull the latest Docker image for Canarytokens using: docker pull canarytokens/canarytokens:latest
  2. Alternatively, pull a Docker image after commit sha-097d91a
  3. Stop the existing Canarytokens container
  4. Start the container with the new image

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41664 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data