{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-28111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-28111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-28111 is a medium-severity code injection vulnerability in thinkst canarytokens, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-28111 and fix it if it is affected.\n\nWhat it is: CVE-2024-28111 is a medium-severity code injection vulnerability in thinkst canarytokens, published on 6 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-28111 in the wild and no public exploit code.\n\nAffected product: thinkst canarytokens. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-28111/ (Markdown: https://insights.sbomify.com/CVE-2024-28111/index.md)","id":"CVE-2024-28111","markdown":"https://insights.sbomify.com/CVE-2024-28111/index.md","name":"CVE-2024-28111","record":{"aliases":["GHSA-fqh6-v4qp-65fv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Canarytokens web service","requires_auth":"none","summary":"Attackers can inject malicious formulas into exported CSV files, leading to code execution when the victim opens the file in spreadsheet software.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"canarytokens","vendor":"thinkst"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CSV Injection in exported history CSV files","id":"CVE-2024-28111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross site scripting on router page in Peering Manager","id":"CVE-2024-28112"},"packages":[],"prev":{"headline":"Go SDK for CloudEvents's use of WithRoundTripper to create a Client leaks credentials","id":"CVE-2024-28110"},"products":["canarytokens"],"published":"2024-03-06","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-9768","kev_date_added":null,"published":"2019-03-14"},{"cvss_score":6.3,"headline":"Cross-Site Scripting in Canarytoken history","id":"CVE-2023-22475","kev_date_added":null,"published":"2023-01-06"},{"cvss_score":6.3,"headline":"Cross-Site Scripting in Canarytoken history","id":"CVE-2022-31113","kev_date_added":null,"published":"2022-07-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["thinkst"]},"summary":"Attackers can inject malicious formulas into exported CSV files, leading to code execution when the victim opens the file in spreadsheet software.","url":"https://insights.sbomify.com/CVE-2024-28111/"}