{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20429 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20429 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20429 is a high-severity memory corruption vulnerability in n/a, published on 27 Jan 2020. 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-20429 and fix it if it is affected.\n\nWhat it is: CVE-2019-20429 is a high-severity memory corruption vulnerability in n/a, published on 27 Jan 2020. 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-20429 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-2019-20429/ (Markdown: https://insights.sbomify.com/CVE-2019-20429/index.md)","id":"CVE-2019-20429","markdown":"https://insights.sbomify.com/CVE-2019-20429/index.md","name":"CVE-2019-20429","record":{"aliases":["GHSA-626m-2fcr-7j48","UBUNTU-CVE-2019-20429"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Lustre file system","requires_auth":"none","summary":"An attacker can cause a system panic and denial of service in the Lustre file system by sending malformed packets with invalid buffer counts.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lustre","vendor":"lustre"}],"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:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds read and panic (via a modified lm_bufcount field) due to the lack of validation for specific fields of packets sent by a client. This is caused by interaction between sptlrpc_svc_unwrap_request and lustre_msg_hdr_size_v2.","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":"Memory corruption in n/a","id":"CVE-2019-20429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-20430"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-20428"},"products":["n/a"],"published":"2020-01-27","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-20427","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2019-20423","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2019-20424","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-20425","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-20426","kev_date_added":null,"published":"2020-01-27"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-20428","kev_date_added":null,"published":"2020-01-27"}],"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":"An attacker can cause a system panic and denial of service in the Lustre file system by sending malformed packets with invalid buffer counts.","url":"https://insights.sbomify.com/CVE-2019-20429/"}