{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-06-14T17:21:11.855","vulnerabilities":[{"cve":{"id":"CVE-2024-41663","sourceIdentifier":"security-advisories@github.com","published":"2024-07-23T16:15:06.070","lastModified":"2026-04-15T00:35:42.020","vulnStatus":"Deferred","cveTags":[],"descriptions":[{"lang":"en","value":"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`."},{"lang":"es","value":"Los Canarytokens ayudan a rastrear la actividad y las acciones en una red. Se identificó una vulnerabilidad de Cross Site Scripting en el Canarytoken \"Cloned Website\", mediante la cual el creador del Canarytoken puede atacarse a sí mismo. El creador de un Canarytoken de redireccionamiento lento puede insertar Javascript en la URL de destino de su token de redireccionamiento lento. Cuando el creador navega más tarde por la página de administración de su propio Canarytoken, se ejecuta Javascript. Este es un XSS propio. Un atacante podría crear un Canarytoken con este XSS propio y enviar el enlace de administración a una víctima. Cuando hacen clic en él, se ejecutará Javascript. Sin embargo, no se revelará ninguna información confidencial (por ejemplo, información de sesión) al actor malicioso. Este problema ya está solucionado en Canarytokens.org. Los usuarios de instalaciones de Canarytokens autohospedadas pueden actualizar extrayendo la última imagen de Docker o cualquier imagen de Docker después de `sha-097d91a`."}],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","baseScore":3.5,"baseSeverity":"LOW","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"LOW","availabilityImpact":"NONE"},"exploitabilityScore":2.1,"impactScore":1.4}]},"weaknesses":[{"source":"security-advisories@github.com","type":"Secondary","description":[{"lang":"en","value":"CWE-79"}]}],"references":[{"url":"https://github.com/thinkst/canarytokens/security/advisories/GHSA-xj9h-3j9c-c95h","source":"security-advisories@github.com"},{"url":"https://github.com/thinkst/canarytokens/security/advisories/GHSA-xj9h-3j9c-c95h","source":"af854a3a-2127-422b-91ae-364da2661108"}]}}]}