CVE-2022-31113 Cross-Site Scripting in Canarytoken history
Attackers can execute JavaScript in the history page of triggered Canarytokens, potentially viewing or modifying token data and exposing creator information.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2022-31113?
CVE-2022-31113 is a medium-severity cross-site scripting vulnerability in thinkst canarytokens, published on 1 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Canarytokens is an open source tool which helps track activity and actions on your network. A Cross-Site Scripting vulnerability was identified in the history page of triggered Canarytokens. This permits an attacker who recognised an HTTP-based Canarytoken (a URL) to execute Javascript in the Canarytoken's 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. An attacker could only act on the discovered Canarytoken. This issue did not expose other Canarytokens or other Canarytoken creators. The issue has been patched on Canarytokens.org and in the latest release. No signs of successful exploitation of this vulnerability have been found. Users are advised to upgrade. There are no known workarounds for this issue.
Weakness: CWE-79
Which versions are affected by CVE-2022-31113?
It affects 1 product.
Products include Thinkst Canarytokens.
How do I fix CVE-2022-31113?
No fix has been published for CVE-2022-31113 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2022-31113 being exploited?
There is no known exploitation of CVE-2022-31113 in the wild and no public exploit code.
Other vulnerabilities in thinkst canarytokens
Sources
Also known as GHSA-5675-3424-hpqr.