{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20391 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-20391 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-20391 and fix it if it is affected.\n\nWhat it is: CVE-2019-20391 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-20391 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-20391/ (Markdown: https://insights.sbomify.com/CVE-2019-20391/index.md)","id":"CVE-2019-20391","markdown":"https://insights.sbomify.com/CVE-2019-20391/index.md","name":"CVE-2019-20391","record":{"aliases":["DEBIAN-CVE-2019-20391","GHSA-57jg-xr2w-54jg","UBUNTU-CVE-2019-20391"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libyang YANG parser","requires_auth":"none","summary":"An invalid memory access in libyang allows attackers to crash applications parsing untrusted YANG files via crafted if-feature statements.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libyang","vendor":"cesnet"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.","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 n/a","id":"CVE-2019-20391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Null dereference in n/a","id":"CVE-2019-20392"},"packages":[],"prev":{"headline":"Subrion CMS Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2019-20390"},"products":["n/a"],"published":"2020-01-22","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-19333","kev_date_added":null,"published":"2019-12-06"},{"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":["n/a"]},"summary":"An invalid memory access in libyang allows attackers to crash applications parsing untrusted YANG files via crafted if-feature statements.","url":"https://insights.sbomify.com/CVE-2019-20391/"}