{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6533 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2018-6533 is a high-severity vulnerability in n/a, published on 27 Feb 2018. 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-2018-6533 and fix it if it is affected.\n\nWhat it is: CVE-2018-6533 is a high-severity vulnerability in n/a, published on 27 Feb 2018. 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-2018-6533 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-2018-6533/ (Markdown: https://insights.sbomify.com/CVE-2018-6533/index.md)","id":"CVE-2018-6533","markdown":"https://insights.sbomify.com/CVE-2018-6533/index.md","name":"CVE-2018-6533","record":{"aliases":["DEBIAN-CVE-2018-6533","GHSA-5f3g-f3qg-cgq4","UBUNTU-CVE-2018-6533"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Icinga monitoring server","requires_auth":"low_privilege","summary":"Attackers with write access to init.conf can escalate privileges to root and execute arbitrary code in Icinga 2.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"icinga","vendor":"icinga"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"An issue was discovered in Icinga 2.x through 2.8.1. By editing the init.conf file, Icinga 2 can be run as root. Following this the program can be used to run arbitrary code as root. This was fixed by no longer using init.conf to determine account information for any root-executed code (a larger issue than CVE-2017-16933).","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":"Privilege escalation in n/a","id":"CVE-2018-6533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2018-6534"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-6532"},"products":["n/a"],"published":"2018-02-27","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.3,"headline":"Icinga Director configuration is susceptible to Cross-Site Request Forgery","id":"CVE-2024-24820","kev_date_added":null,"published":"2024-02-09"},{"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-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with write access to init.conf can escalate privileges to root and execute arbitrary code in Icinga 2.","url":"https://insights.sbomify.com/CVE-2018-6533/"}