{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45207 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-45207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-45207 is a high-severity vulnerability in Veeam Agent for Windows, published on 4 Dec 2024. 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-45207 and fix it if it is affected.\n\nWhat it is: CVE-2024-45207 is a high-severity vulnerability in Veeam Agent for Windows, published on 4 Dec 2024. 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-45207 in the wild and no public exploit code.\n\nAffected product: Veeam Agent for Windows. 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-45207/ (Markdown: https://insights.sbomify.com/CVE-2024-45207/index.md)","id":"CVE-2024-45207","markdown":"https://insights.sbomify.com/CVE-2024-45207/index.md","name":"CVE-2024-45207","record":{"aliases":["GHSA-69h8-2gjf-xq29"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Veeam Agent for Windows","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by placing malicious DLLs in insecure PATH directories, potentially leading to unauthorized access or data theft.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"veeam_agent_for_windows","vendor":"veeam"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"DLL injection in Veeam Agent for Windows can occur if the system's PATH variable includes insecure locations. When the agent runs, it searches these directories for necessary DLLs. If an attacker places a malicious DLL in one of these directories, the Veeam Agent might load it inadvertently, allowing the attacker to execute harmful code. This could lead to unauthorized access, data theft, or disruption of services","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":"Other in Agent for Windows","id":"CVE-2024-45207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Director","id":"CVE-2024-45208"},"packages":[],"prev":{"headline":"Server-side request forgery in Service Provider Console","id":"CVE-2024-45206"},"products":["Agent for Windows"],"published":"2024-12-04","related":[{"cvss_score":7.8,"headline":"Auth bypass in Agent for Windows","id":"CVE-2024-29853","kev_date_added":null,"published":"2024-05-22"},{"cvss_score":7.3,"headline":"Privilege escalation in Agent for Microsoft Windows","id":"CVE-2025-48982","kev_date_added":null,"published":"2025-10-30"}],"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":"2024-12-04","vendors":["Veeam"]},"summary":"Attackers can execute arbitrary code by placing malicious DLLs in insecure PATH directories, potentially leading to unauthorized access or data theft.","url":"https://insights.sbomify.com/CVE-2024-45207/"}