{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45412 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45412 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45412 is a medium-severity denial of service vulnerability in yeti-platform yeti, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-45412 and fix it if it is affected.\n\nWhat it is: CVE-2024-45412 is a medium-severity denial of service vulnerability in yeti-platform yeti, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-45412 in the wild and no public exploit code.\n\nAffected product: yeti-platform yeti. 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-45412/ (Markdown: https://insights.sbomify.com/CVE-2024-45412/index.md)","id":"CVE-2024-45412","markdown":"https://insights.sbomify.com/CVE-2024-45412/index.md","name":"CVE-2024-45412","record":{"aliases":["GHSA-cwwm-pq9x-2cxv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Forensics Intelligence Platform","requires_auth":"none","summary":"Remote attackers can cause denial of service in Yeti by sending Unicode payloads that trigger expensive normalization on Windows systems.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"yeti","vendor":"yeti-platform"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Remote user-controlled data tags can reach a Unicode normalization with a compatibility form NFKD. Under Windows, such normalization is costly in resources and may lead to denial of service with attacks such as One Million Unicode payload. This can get worse with the use of special Unicode characters like U+2100 (℀), or U+2105 (℅) which could lead the payload size to be tripled. Versions prior to 2.1.11 are affected by this vulnerability. The patch is included in 2.1.11.","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":"Yeti affected by a Potential Denial of Service due to the One Milion Unicode characters attack","id":"CVE-2024-45412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-45413"},"packages":[],"prev":{"headline":"Twig has a possible sandbox bypass","id":"CVE-2024-45411"},"products":["yeti"],"published":"2024-09-10","related":[{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-46508","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":7.3,"headline":"Code injection in n/a","id":"CVE-2024-46507","kev_date_added":null,"published":"2026-05-08"}],"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-09-10","vendors":["yeti-platform"]},"summary":"Remote attackers can cause denial of service in Yeti by sending Unicode payloads that trigger expensive normalization on Windows systems.","url":"https://insights.sbomify.com/CVE-2024-45412/"}