First published: Tue Jul 23 2024(Updated: )
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`.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
>=sha-097d91a |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-41663 has been classified as a moderate severity Cross-Site Scripting vulnerability.
To fix CVE-2024-41663, ensure you update to the latest version of Canarytokens where the vulnerability has been patched.
CVE-2024-41663 affects users of the Canarytokens software, particularly those utilizing the 'Cloned Website' Canarytoken feature.
CVE-2024-41663 is a Cross-Site Scripting vulnerability that allows a creator of a Canarytoken to inadvertently execute malicious JavaScript.
Yes, CVE-2024-41663 can compromise network security by enabling self-inflicted attacks via malicious scripts in created Canarytokens.