{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-14312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-14312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-14312 is a high-severity vulnerability in n/a, published on 11 Sep 2017. 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-2017-14312 and fix it if it is affected.\n\nWhat it is: CVE-2017-14312 is a high-severity vulnerability in n/a, published on 11 Sep 2017. 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-2017-14312 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-2017-14312/ (Markdown: https://insights.sbomify.com/CVE-2017-14312/index.md)","id":"CVE-2017-14312","markdown":"https://insights.sbomify.com/CVE-2017-14312/index.md","name":"CVE-2017-14312","record":{"aliases":["GHSA-3j4j-7q69-wj53"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Nagios Core monitoring","requires_auth":"low_privilege","summary":"Local users can gain privileges if Nagios binaries or configs are owned by non-root accounts, requiring specific non-default file ownership settings.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nagios_core","vendor":"nagios"}],"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":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Nagios Core through 4.3.4 initially executes /usr/sbin/nagios as root but supports configuration options in which this file is owned by a non-root account (and similarly can have nagios.cfg owned by a non-root account), which allows local users to gain privileges by leveraging access to this non-root account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privilege escalation in n/a","id":"CVE-2017-14312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-14313"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2017-14311"},"products":["n/a"],"published":"2017-09-11","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-35269","kev_date_added":null,"published":"2020-12-23"},{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2018-13457","kev_date_added":null,"published":"2018-07-12"},{"cvss_score":5.5,"headline":"Null dereference in n/a","id":"CVE-2018-13458","kev_date_added":null,"published":"2018-07-12"}],"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-05","vendors":["n/a"]},"summary":"Local users can gain privileges if Nagios binaries or configs are owned by non-root accounts, requiring specific non-default file ownership settings.","url":"https://insights.sbomify.com/CVE-2017-14312/"}