{"answers":{"affected":"1 open source package ship an affected version, including github.com/wazuh/wazuh. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-35177 in the wild and no public exploit code.","fix":"Upgrade github.com/wazuh/wazuh to 4.9.0+incompatible or later.","what":"CVE-2024-35177 is a high-severity vulnerability in Wazuh Wazuh, published on 3 Feb 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-35177 and fix it if it is affected.\n\nWhat it is: CVE-2024-35177 is a high-severity vulnerability in Wazuh Wazuh, published on 3 Feb 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-35177 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/wazuh/wazuh (Go): affected from 3.0.0+incompatible; fixed in 4.9.0+incompatible\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-35177/ (Markdown: https://insights.sbomify.com/CVE-2024-35177/index.md)","id":"CVE-2024-35177","markdown":"https://insights.sbomify.com/CVE-2024-35177/index.md","name":"CVE-2024-35177","record":{"aliases":["GHSA-pmr2-2r83-h3cv","GO-2025-3444"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Wazuh agent","requires_auth":"low_privilege","summary":"A local attacker can escalate privileges to SYSTEM by placing malicious DLLs in the Wazuh agent installation directory when a non-default path is used.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wazuh","vendor":"wazuh"}],"cvss":{"score":7.8,"severity":"high","source":"cna","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-284","name":"Improper Access Control"}],"description":"Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. The wazuh-agent for Windows is vulnerable to a Local Privilege Escalation vulnerability due to improper ACL of the non-default installation directory. A local malicious user could potentially exploit this vulnerability by placing one of the many DLL that are loaded and not present on the system in the installation folder of the agent OR by replacing the service executable binary itself with a malicious one. The root cause is an improper ACL applied on the installation folder when a non-default installation path is specified (e.g,: C:\\wazuh). Many DLLs are loaded from the installation folder and by creating a malicious DLLs that exports the functions of a legit one (and that is not found on the system where the agent is installed, such as rsync.dll) it is possible to escalate privileges from a low-privileged user and obtain code execution under the context of NT AUTHORITY\\SYSTEM. This issue has been addressed in version 4.9.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Access Control in wazuh-agent","id":"CVE-2024-35177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":"wazuh:wazuh","products":["wazuh:wazuh"],"type":"privilege_escalation","year":"2024"},"n_packages":1,"n_references":1,"next":{"headline":"Jupyter server on Windows discloses Windows user password hash","id":"CVE-2024-35178"},"packages":[{"ecosystem":"Go","fixed":["4.9.0+incompatible"],"introduced":["3.0.0+incompatible"],"last_affected":[],"package":"github.com/wazuh/wazuh","purl":"pkg:golang/github.com/wazuh/wazuh","source":"GO-2025-3444"}],"prev":{"headline":"REXML contains a denial of service vulnerability","id":"CVE-2024-35176"},"products":["wazuh"],"published":"2025-02-03","related":[{"cvss_score":9.9,"headline":"Wazuh Server Deserialization of Untrusted Data","id":"CVE-2025-24016","kev_date_added":"2025-06-10","published":"2025-02-10"},{"cvss_score":9.8,"headline":"Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2024-32038","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-44079","kev_date_added":null,"published":"2021-11-22"},{"cvss_score":9.5,"headline":"Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft","id":"CVE-2024-1243","kev_date_added":null,"published":"2025-06-11"},{"cvss_score":9.1,"headline":"Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)","id":"CVE-2026-61800","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":9.1,"headline":"Wazuh: merged-file header path traversal in cluster sync allows arbitrary file write under WAZUH_PATH in Wazuh manager","id":"CVE-2026-48024","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":9.1,"headline":"Path traversal in wazuh","id":"CVE-2026-48162","kev_date_added":null,"published":"2026-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-02-04","vendors":["wazuh"]},"summary":"A local attacker can escalate privileges to SYSTEM by placing malicious DLLs in the Wazuh agent installation directory when a non-default path is used.","url":"https://insights.sbomify.com/CVE-2024-35177/"}