{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-41664 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41664 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-41664 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2024-41664 in the wild and no public exploit code.\n\nAffected product: thinkst canarytokens. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-41664/ (Markdown: https://insights.sbomify.com/CVE-2024-41664/index.md)","id":"CVE-2024-41664","markdown":"https://insights.sbomify.com/CVE-2024-41664/index.md","name":"CVE-2024-41664","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Canarytokens web service","requires_auth":"low_privilege","summary":"Attackers can exploit a blind SSRF in the webhook feature to map internal network ports and access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Blind SSRF via Canarytoken Webhook","id":"CVE-2024-41664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Ampache Stored Cross-site Scripting Vulnerability","id":"CVE-2024-41665"},"packages":[],"prev":{"headline":"Canarytoken \"Cloned Website\" Vulnerable to Stored Cross-Site Scripting","id":"CVE-2024-41663"},"products":["canarytokens"],"published":"2024-07-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["thinkst"]},"summary":"Attackers can exploit a blind SSRF in the webhook feature to map internal network ports and access internal resources.","url":"https://insights.sbomify.com/CVE-2024-41664/"}