{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-19333 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-19333 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 6 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-19333 and fix it if it is affected.\n\nWhat it is: CVE-2019-19333 is a high-severity memory corruption vulnerability in Redhat Enterprise Linux, published on 6 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-19333 in the wild and no public exploit code.\n\nAffected product: Redhat Enterprise Linux. 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-19333/ (Markdown: https://insights.sbomify.com/CVE-2019-19333/index.md)","id":"CVE-2019-19333","markdown":"https://insights.sbomify.com/CVE-2019-19333/index.md","name":"CVE-2019-19333","record":{"aliases":["DEBIAN-CVE-2019-19333","GHSA-68cw-w9pp-fc96"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"YANG parsing library","requires_auth":"none","summary":"A stack-based buffer overflow in libyang allows attackers to cause denial of service or execute code via malicious YANG files.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"libyang","vendor":"cesnet"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of type \"bits\". An application that uses libyang to parse untrusted YANG files may be vulnerable to this flaw, which would allow an attacker to cause a denial of service or possibly gain code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in libyang","id":"CVE-2019-19333","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:enterprise_linux","products":["redhat:enterprise_linux"],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in libyang","id":"CVE-2019-19334"},"packages":[],"prev":{"headline":"Memory corruption in Kernel","id":"CVE-2019-19332"},"products":["libyang"],"published":"2019-12-06","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-20393","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2019-20394","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2019-20397","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":8.1,"headline":"Memory corruption in libyang","id":"CVE-2019-19334","kev_date_added":null,"published":"2019-12-06"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2023-26917","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2021-28902","kev_date_added":null,"published":"2021-05-20"}],"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":["Red Hat"]},"summary":"A stack-based buffer overflow in libyang allows attackers to cause denial of service or execute code via malicious YANG files.","url":"https://insights.sbomify.com/CVE-2019-19333/"}