{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-56497 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-56497 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-56497 is a medium-severity command injection vulnerability in Fortinet FortiMail, published on 14 Jan 2025. 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-2024-56497 and fix it if it is affected.\n\nWhat it is: CVE-2024-56497 is a medium-severity command injection vulnerability in Fortinet FortiMail, published on 14 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-56497 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiMail. 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-56497/ (Markdown: https://insights.sbomify.com/CVE-2024-56497/index.md)","id":"CVE-2024-56497","markdown":"https://insights.sbomify.com/CVE-2024-56497/index.md","name":"CVE-2024-56497","record":{"aliases":["GHSA-8qhx-f4vg-5h4h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fortinet email security","requires_auth":"high_privilege","summary":"Attackers can execute unauthorized commands via the CLI in FortiMail and FortiRecorder due to improper neutralization of special elements.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortimail","vendor":"fortinet"},{"product":"fortirecorder","vendor":"fortinet"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:X","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiMail versions 7.2.0 through 7.2.4 and 7.0.0 through 7.0.6 and 6.4.0 through 6.4.7, FortiRecorder versions 7.0.0 and 6.4.0 through 6.4.4 allows attacker to execute unauthorized code or commands via the CLI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in FortiMail","id":"CVE-2024-56497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Not used","id":"CVE-2024-56498"},"packages":[],"prev":{"headline":"IBM EntireX information disclosure","id":"CVE-2024-56496"},"products":["FortiMail","FortiRecorder"],"published":"2025-01-14","related":[{"cvss_score":9.8,"headline":"Fortinet FortiMail Path Traversal","id":"CVE-2026-104286","kev_date_added":"2026-10-01","published":"2026-10-01"},{"cvss_score":9.8,"headline":"Auth bypass in Fortinet FortiMail","id":"CVE-2021-36166","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":9.8,"headline":"SQL injection in Fortinet FortiMail","id":"CVE-2021-24007","kev_date_added":null,"published":"2021-07-09"},{"cvss_score":9.8,"headline":"Auth bypass in FortiMail","id":"CVE-2020-9294","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":9,"headline":"Auth bypass in FortiMail","id":"CVE-2023-47539","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.8,"headline":"Path traversal in Fortinet FortiMail","id":"CVE-2021-24013","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":8.8,"headline":"Memory corruption in Fortinet FortiMail","id":"CVE-2021-22129","kev_date_added":null,"published":"2021-07-09"}],"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":"total"},"state":"PUBLISHED","updated":"2025-01-14","vendors":["Fortinet"]},"summary":"Attackers can execute unauthorized commands via the CLI in FortiMail and FortiRecorder due to improper neutralization of special elements.","url":"https://insights.sbomify.com/CVE-2024-56497/"}