{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28909 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28909 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28909 is a high-severity vulnerability in n/a, published on 24 May 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-28909 and fix it if it is affected.\n\nWhat it is: CVE-2020-28909 is a high-severity vulnerability in n/a, published on 24 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-28909 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-28909/ (Markdown: https://insights.sbomify.com/CVE-2020-28909/index.md)","id":"CVE-2020-28909","markdown":"https://insights.sbomify.com/CVE-2020-28909/index.md","name":"CVE-2020-28909","record":{"aliases":["GHSA-fj4q-mmcw-p43v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Nagios Fusion","requires_auth":"low_privilege","summary":"Low-privilege users can escalate to root by modifying scripts executed via sudo due to incorrect file permissions in Nagios Fusion.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fusion","vendor":"nagios"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Incorrect File Permissions in Nagios Fusion 4.1.8 and earlier allows for Privilege Escalation to root via modification of scripts. Low-privileges users are able to modify files that can be executed by sudo.","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":"Privilege escalation in n/a","id":"CVE-2020-28909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-28910"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2020-28908"},"products":["n/a"],"published":"2021-05-24","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-28900","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-28901","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-28902","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-28904","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-28907","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-28908","kev_date_added":null,"published":"2021-05-24"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2020-28905","kev_date_added":null,"published":"2021-05-24"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Low-privilege users can escalate to root by modifying scripts executed via sudo due to incorrect file permissions in Nagios Fusion.","url":"https://insights.sbomify.com/CVE-2020-28909/"}