{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24820 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2024-24820 is a high-severity vulnerability in icingaweb2-module-director, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-24820 and fix it if it is affected.\n\nWhat it is: CVE-2024-24820 is a high-severity vulnerability in icingaweb2-module-director, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24820 exists.\n\nAffected product: icingaweb2-module-director. 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-24820/ (Markdown: https://insights.sbomify.com/CVE-2024-24820/index.md)","id":"CVE-2024-24820","markdown":"https://insights.sbomify.com/CVE-2024-24820/index.md","name":"CVE-2024-24820","record":{"aliases":["DEBIAN-CVE-2024-24820","GHSA-3mwp-5p5v-j6q3","UBUNTU-CVE-2024-24820"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Icinga Director module","requires_auth":"high_privilege","summary":"Attackers can perform unauthorized changes to the monitoring environment via CSRF, requiring users to upgrade Icinga Director.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga","vendor":"icinga"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Icinga Director is a tool designed to make Icinga 2 configuration handling easy. Not any of Icinga Director's configuration forms used to manipulate the monitoring environment are protected against cross site request forgery (CSRF). It enables attackers to perform changes in the monitoring environment managed by Icinga Director without the awareness of the victim. Users of the map module in version 1.x, should immediately upgrade to v2.0. The mentioned XSS vulnerabilities in Icinga Web are already fixed as well and upgrades to the most recent release of the 2.9, 2.10 or 2.11 branch must be performed if not done yet. Any later major release is also suitable. Icinga Director will receive minor updates to the 1.8, 1.9, 1.10 and 1.11 branches to remedy this issue. Upgrade immediately to a patched release. If that is not feasible, disable the director module for the time being.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Icinga Director configuration is susceptible to Cross-Site Request Forgery","id":"CVE-2024-24820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":6,"next":{"headline":"Code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php in Composer","id":"CVE-2024-24821"},"packages":[],"prev":{"headline":"icingaweb2-module-incubator base implementation for HTML forms is susceptible to CSRF","id":"CVE-2024-24819"},"products":["icingaweb2-module-director"],"published":"2024-02-09","related":[{"cvss_score":9.3,"headline":"Icinga 2 certificate renewal might incorrectly renew an invalid certificate","id":"CVE-2025-48057","kev_date_added":null,"published":"2025-05-27"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-29663","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-6535","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2020-14004","kev_date_added":null,"published":"2020-06-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-6533","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16882","kev_date_added":null,"published":"2017-11-18"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["Icinga"]},"summary":"Attackers can perform unauthorized changes to the monitoring environment via CSRF, requiring users to upgrade Icinga Director.","url":"https://insights.sbomify.com/CVE-2024-24820/"}