{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-41663 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41663 is a low-severity cross-site scripting vulnerability in thinkst canarytokens, published on 23 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-41663 and fix it if it is affected.\n\nWhat it is: CVE-2024-41663 is a low-severity cross-site scripting vulnerability in thinkst canarytokens, published on 23 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-41663 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-41663/ (Markdown: https://insights.sbomify.com/CVE-2024-41663/index.md)","id":"CVE-2024-41663","markdown":"https://insights.sbomify.com/CVE-2024-41663/index.md","name":"CVE-2024-41663","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Canarytokens web service","requires_auth":"low_privilege","summary":"Attackers can inject JavaScript into Canarytoken management pages, executing code in victims' browsers via self-XSS vectors.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Canarytokens help track activity and actions on a network.  A Cross-Site Scripting vulnerability was identified in the \"Cloned Website\" Canarytoken, whereby the Canarytoken's creator can attack themselves. The creator of a slow-redirect Canarytoken can insert Javascript into the destination URL of their slow redirect token. When the creator later browses the management page for their own Canarytoken, the Javascript executes. This is a self-XSS. An attacker could create a Canarytoken with this self-XSS, and send the management link to a victim. When they click on it, the Javascript would execute. However, no sensitive information (ex. session information) will be disclosed to the malicious actor. 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":"Canarytoken \"Cloned Website\" Vulnerable to Stored Cross-Site Scripting","id":"CVE-2024-41663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Blind SSRF via Canarytoken Webhook","id":"CVE-2024-41664"},"packages":[],"prev":{"headline":"VNote vulnerable to Markdown XSS, which leads to RCE","id":"CVE-2024-41662"},"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 inject JavaScript into Canarytoken management pages, executing code in victims' browsers via self-XSS vectors.","url":"https://insights.sbomify.com/CVE-2024-41663/"}