{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-36469 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-36469 is a low-severity vulnerability in Zabbix Zabbix, published on 2 Apr 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-36469 and fix it if it is affected.\n\nWhat it is: CVE-2024-36469 is a low-severity vulnerability in Zabbix Zabbix, published on 2 Apr 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-36469 in the wild and no public exploit code.\n\nAffected product: Zabbix Zabbix. 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-36469/ (Markdown: https://insights.sbomify.com/CVE-2024-36469/index.md)","id":"CVE-2024-36469","markdown":"https://insights.sbomify.com/CVE-2024-36469/index.md","name":"CVE-2024-36469","record":{"aliases":["DEBIAN-CVE-2024-36469","GHSA-8w6w-prh9-wr2j","UBUNTU-CVE-2024-36469"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Zabbix monitoring system","requires_auth":"none","summary":"Attackers can enumerate valid usernames in Zabbix by analyzing login response timing differences, facilitating targeted credential attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Zabbix","cpe":[{"product":"zabbix","vendor":"zabbix"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one.","ecosystems":[],"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":"User enumeration via timing attack in Zabbix web interface","id":"CVE-2024-36469","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"zabbix:zabbix","products":["zabbix:zabbix"],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in TeamCity","id":"CVE-2024-36470"},"packages":[],"prev":{"headline":"Stack buffer overflow in zbx_snmp_cache_handle_engineid","id":"CVE-2024-36468"},"products":["Zabbix"],"published":"2025-04-02","related":[{"cvss_score":9.1,"headline":"Zabbix Frontend Authentication Bypass","id":"CVE-2022-23131","kev_date_added":"2022-02-22","published":"2022-01-13"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-0640","kev_date_added":null,"published":"2007-01-31"},{"cvss_score":9.9,"headline":"SQL injection in user.get API","id":"CVE-2024-42327","kev_date_added":null,"published":"2024-11-27"},{"cvss_score":9.9,"headline":"Remote code execution within ping script","id":"CVE-2024-22116","kev_date_added":null,"published":"2024-08-09"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2013-3738","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2013-5743","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-10134","kev_date_added":null,"published":"2017-02-16"}],"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":"2025-11-03","vendors":["Zabbix"]},"summary":"Attackers can enumerate valid usernames in Zabbix by analyzing login response timing differences, facilitating targeted credential attacks.","url":"https://insights.sbomify.com/CVE-2024-36469/"}