{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-14610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-14610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-14610 is a high-severity vulnerability in n/a, published on 20 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-14610 and fix it if it is affected.\n\nWhat it is: CVE-2017-14610 is a high-severity vulnerability in n/a, published on 20 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-14610 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-14610/ (Markdown: https://insights.sbomify.com/CVE-2017-14610/index.md)","id":"CVE-2017-14610","markdown":"https://insights.sbomify.com/CVE-2017-14610/index.md","name":"CVE-2017-14610","record":{"aliases":["UBUNTU-CVE-2017-14610"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bareos backup software","requires_auth":"low_privilege","summary":"Local attackers can kill arbitrary processes or escalate privileges by modifying the PID file before root scripts execute kill commands.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bareos","vendor":"bareos"}],"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-665","name":"Improper Initialization"}],"description":"bareos-dir, bareos-fd, and bareos-sd in bareos-core in Bareos 16.2.6 and earlier create a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a \"kill `cat /pathname`\" command.","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":"Race condition in n/a","id":"CVE-2017-14610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2017-14611"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2017-14609"},"products":["n/a"],"published":"2017-09-20","related":[{"cvss_score":8.1,"headline":"Incorrect Authorization in Bareos Director","id":"CVE-2022-24755","kev_date_added":null,"published":"2022-03-15"},{"cvss_score":7.5,"headline":"Missing Release of Memory after Effective Lifetime in Bareos Director","id":"CVE-2022-24756","kev_date_added":null,"published":"2022-03-15"},{"cvss_score":6.8,"headline":"Authentication bypass in Bareos","id":"CVE-2020-4042","kev_date_added":null,"published":"2020-07-10"},{"cvss_score":6,"headline":"Heap-based Buffer Overflow in Bareos Director","id":"CVE-2020-11061","kev_date_added":null,"published":"2020-07-10"}],"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-09-16","vendors":["n/a"]},"summary":"Local attackers can kill arbitrary processes or escalate privileges by modifying the PID file before root scripts execute kill commands.","url":"https://insights.sbomify.com/CVE-2017-14610/"}