{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-2389 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-2389 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-2389 is a medium-severity vulnerability in Mongodb Mongodb, published on 30 Aug 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-2389 and fix it if it is affected.\n\nWhat it is: CVE-2019-2389 is a medium-severity vulnerability in Mongodb Mongodb, published on 30 Aug 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-2389 in the wild and no public exploit code.\n\nAffected product: Mongodb Mongodb. 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-2019-2389/ (Markdown: https://insights.sbomify.com/CVE-2019-2389/index.md)","id":"CVE-2019-2389","markdown":"https://insights.sbomify.com/CVE-2019-2389/index.md","name":"CVE-2019-2389","record":{"aliases":["GHSA-vjcf-4g29-6hfr"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MongoDB Server","requires_auth":"low_privilege","summary":"Users with write access to the PID file can kill arbitrary processes when root stops MongoDB, leading to privilege escalation or denial of service.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"mongodb","vendor":"mongodb"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Incorrect scoping of kill operations in MongoDB Server's packaged SysV init scripts allow users with write access to the PID file to insert arbitrary PIDs to be killed when the root user stops the MongoDB process via SysV init. This issue affects MongoDB Server v4.0 versions prior to 4.0.11; MongoDB Server v3.6 versions prior to 3.6.14; MongoDB Server v3.4 versions prior to 3.4.22.","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":"Process termination via PID file manipulation","id":"CVE-2019-2389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mongodb:mongodb","products":["mongodb:mongodb"],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Code execution on Windows via OpenSSL engine injection","id":"CVE-2019-2390"},"packages":[],"prev":{"headline":"Potential exposure of log information in Ops Manager","id":"CVE-2019-2388"},"products":["MongoDB Server"],"published":"2019-08-30","related":[{"cvss_score":8.7,"headline":"MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency","id":"CVE-2025-14847","kev_date_added":"2025-12-29","published":"2025-12-19"},{"cvss_score":9.2,"headline":"Auth bypass in MongoDB Server","id":"CVE-2026-82067","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.2,"headline":"MongoDB Improper Input Validation in Compute Mode External Data Processing Leading to Memory Corruption","id":"CVE-2026-13072","kev_date_added":null,"published":"2026-07-22"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2017-15535","kev_date_added":null,"published":"2017-11-01"},{"cvss_score":9,"headline":"Improper Authentication in MongoDB Intra-Cluster Connections Allows Credential Exposure","id":"CVE-2026-18691","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":8.8,"headline":"MongoDB Server may allow successful untrusted connection","id":"CVE-2024-1351","kev_date_added":null,"published":"2024-03-07"},{"cvss_score":8.7,"headline":"Denial of service in MongoDB Server","id":"CVE-2026-82064","kev_date_added":null,"published":"2026-09-08"}],"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":["MongoDB Inc."]},"summary":"Users with write access to the PID file can kill arbitrary processes when root stops MongoDB, leading to privilege escalation or denial of service.","url":"https://insights.sbomify.com/CVE-2019-2389/"}