{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20427 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20427 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20427 is a critical 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-20427 and fix it if it is affected.\n\nWhat it is: CVE-2019-20427 is a critical 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-20427 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-20427/ (Markdown: https://insights.sbomify.com/CVE-2019-20427/index.md)","id":"CVE-2019-20427","markdown":"https://insights.sbomify.com/CVE-2019-20427/index.md","name":"CVE-2019-20427","record":{"aliases":["GHSA-2m5c-rmhj-5qvf","UBUNTU-CVE-2019-20427"],"analysis":{"component_type":"kernel","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Lustre file system","requires_auth":"none","summary":"A signedness error in the Lustre file system kernel module allows remote attackers to cause a panic or potentially execute code via crafted packets.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lustre","vendor":"lustre"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"In the Lustre file system before 2.12.3, the ptlrpc module has a buffer overflow and panic, and possibly remote code execution, due to the lack of validation for specific fields of packets sent by a client. Interaction between req_capsule_get_size and tgt_brw_write leads to a tgt_shortio2pages integer signedness error.","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":"Integer overflow in n/a","id":"CVE-2019-20427","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-20428"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-20426"},"products":["n/a"],"published":"2020-01-27","related":[{"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"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-20429","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":"A signedness error in the Lustre file system kernel module allows remote attackers to cause a panic or potentially execute code via crafted packets.","url":"https://insights.sbomify.com/CVE-2019-20427/"}