Impact
A Cross-Site Scripting vulnerability was identified in the history page of triggered Canarytokens.
An attacker who discovers an HTTP-based Canarytoken (a URL) can use this to execute Javascript in the Canarytoken's trigger history page (domain: canarytokens.org) when the history page is later visited by the Canarytoken's creator.
This vulnerability could be used to disable or delete the affected Canarytoken, or view its activation history. It might also be used as a stepping stone towards revealing more information about the Canarytoken's creator to the attacker. For example, an attacker could recover the email address tied to the Canarytoken, or place Javascript on the history page that redirect the creator towards an attacker-controlled Canarytoken to show the creator's network location.
This vulnerability is similar to GHSA-5675-3424-hpqr, but affected parameters reported differently from the Canarytoken trigger request.
Scope of impact
An attacker could only act on the discovered Canarytoken. This issue did not expose other Canarytokens or other Canarytoken creators.
Patches
This issue is now patched on Canarytokens.org. We scanned Canarytokens.org for signs of malicious exploitation and did not find any.
Users of self-hosted Canarytokens installations can update by pulling the latest Docker image (or any Docker image after sha-fb61290):
$ docker pull thinkst/canarytokens:latest
proximuspl Analyst
Impact
A Cross-Site Scripting vulnerability was identified in the history page of triggered Canarytokens.
An attacker who discovers an HTTP-based Canarytoken (a URL) can use this to execute Javascript in the Canarytoken's trigger history page (domain: canarytokens.org) when the history page is later visited by the Canarytoken's creator.
This vulnerability could be used to disable or delete the affected Canarytoken, or view its activation history. It might also be used as a stepping stone towards revealing more information about the Canarytoken's creator to the attacker. For example, an attacker could recover the email address tied to the Canarytoken, or place Javascript on the history page that redirect the creator towards an attacker-controlled Canarytoken to show the creator's network location.
This vulnerability is similar to GHSA-5675-3424-hpqr, but affected parameters reported differently from the Canarytoken trigger request.
Scope of impact
An attacker could only act on the discovered Canarytoken. This issue did not expose other Canarytokens or other Canarytoken creators.
Patches
This issue is now patched on Canarytokens.org. We scanned Canarytokens.org for signs of malicious exploitation and did not find any.
Users of self-hosted Canarytokens installations can update by pulling the latest Docker image (or any Docker image after sha-fb61290):