{"answers":{"affected":"2 open source packages ship an affected version, including bson-objectid. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19729 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19729 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19729 is a high-severity vulnerability in n/a, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19729 and fix it if it is affected.\n\nWhat it is: CVE-2019-19729 is a high-severity vulnerability in n/a, published on 11 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19729 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bson-objectid (npm): affected all versions up to 1.3.0; no fix listed\n- bson-objectid (npm): affected all versions up to 1.3.0; no fix listed\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-19729/ (Markdown: https://insights.sbomify.com/CVE-2019-19729/index.md)","id":"CVE-2019-19729","markdown":"https://insights.sbomify.com/CVE-2019-19729/index.md","name":"CVE-2019-19729","record":{"aliases":["GHSA-p84x-5xx8-hff9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js BSON library","requires_auth":"none","summary":"Attackers can bypass ObjectID formatting validation by injecting a specific property, potentially leading to data integrity issues in applications using the library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bson-objectid","vendor":"bson-objectid_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"}],"description":"An issue was discovered in the BSON ObjectID (aka bson-objectid) package 1.3.0 for Node.js. ObjectID() allows an attacker to generate a malformed objectid by inserting an additional property to the user-input, because bson-objectid will return early if it detects _bsontype==ObjectID in the user-input object. As a result, objects in arbitrary forms can bypass formatting if they have a valid bsontype.","ecosystems":["npm"],"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":"bson-objectid contains Improper input validation","id":"CVE-2019-19729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-19731"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"bson-objectid","purl":null,"source":"GHSA-p84x-5xx8-hff9"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.0"],"package":"bson-objectid","purl":"pkg:npm/bson-objectid","source":"GHSA-p84x-5xx8-hff9"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19728"},"products":["n/a"],"published":"2019-12-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Attackers can bypass ObjectID formatting validation by injecting a specific property, potentially leading to data integrity issues in applications using the library.","url":"https://insights.sbomify.com/CVE-2019-19729/"}