{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45639 exists.","fix":"No fix has been published for CVE-2022-45639 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-45639 is a high-severity command injection vulnerability in n/a, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-45639 and fix it if it is affected.\n\nWhat it is: CVE-2022-45639 is a high-severity command injection vulnerability in n/a, published on 24 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45639 exists.\n\nAffected product: n/a. 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-2022-45639/ (Markdown: https://insights.sbomify.com/CVE-2022-45639/index.md)","id":"CVE-2022-45639","markdown":"https://insights.sbomify.com/CVE-2022-45639/index.md","name":"CVE-2022-45639","record":{"aliases":["GHSA-v833-mfjc-7qr5"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SleuthKit forensic tool","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands via a crafted parameter in the SleuthKit fls tool, though the severity is disputed by third parties.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"the_sleuth_kit","vendor":"sleuthkit"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"OS Command injection vulnerability in sleuthkit fls tool 4.11.1 allows attackers to execute arbitrary commands via a crafted value to the m parameter. NOTE: third parties have disputed this because there is no analysis showing that the backtick command executes outside the context of the user account that entered the command line.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2023-04-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-04-03","kind":"exploitdb","ref":"51225","stars":null,"title":"sleuthkit 4.11.1 - Command Injection"}],"tier":"weaponised"},"has_fix":false,"headline":"Command injection in n/a","id":"CVE-2022-45639","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-45640"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-45637"},"products":["n/a"],"published":"2023-01-24","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14531","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-10233","kev_date_added":null,"published":"2020-03-08"},{"cvss_score":8.4,"headline":"Sleuth Kit tsk_recover Path Traversal","id":"CVE-2026-40024","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11737","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11738","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11739","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11740","kev_date_added":null,"published":"2018-06-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-02","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via a crafted parameter in the SleuthKit fls tool, though the severity is disputed by third parties.","url":"https://insights.sbomify.com/CVE-2022-45639/"}