{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20005 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-20005 is a medium-severity memory corruption vulnerability in n/a, published on 26 Dec 2019. 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-20005 and fix it if it is affected.\n\nWhat it is: CVE-2019-20005 is a medium-severity memory corruption vulnerability in n/a, published on 26 Dec 2019. 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-20005 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-20005/ (Markdown: https://insights.sbomify.com/CVE-2019-20005/index.md)","id":"CVE-2019-20005","markdown":"https://insights.sbomify.com/CVE-2019-20005/index.md","name":"CVE-2019-20005","record":{"aliases":["DEBIAN-CVE-2019-20005","GHSA-63xx-5fx7-r7rm","UBUNTU-CVE-2019-20005"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ezXML library","requires_auth":"none","summary":"A heap-based buffer over-read in ezXML allows attackers to cause denial of service or disclose sensitive memory contents via crafted XML files.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ezxml","vendor":"ezxml_project"}],"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-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in ezXML 0.8.3 through 0.8.6. The function ezxml_decode, while parsing a crafted XML file, performs incorrect memory handling, leading to a heap-based buffer over-read while running strchr() starting with a pointer after a '\\0' character (where the processing of a string was finished).","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-20005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in n/a","id":"CVE-2019-20006"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2019-20004"},"products":["n/a"],"published":"2019-12-26","related":[{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2021-26220","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2021-26221","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2021-26222","kev_date_added":null,"published":"2021-02-08"},{"cvss_score":7.5,"headline":"Use after free in n/a","id":"CVE-2019-20006","kev_date_added":null,"published":"2019-12-26"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2022-30045","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2019-20198","kev_date_added":null,"published":"2019-12-31"},{"cvss_score":6.5,"headline":"Null dereference in n/a","id":"CVE-2019-20199","kev_date_added":null,"published":"2019-12-31"}],"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 heap-based buffer over-read in ezXML allows attackers to cause denial of service or disclose sensitive memory contents via crafted XML files.","url":"https://insights.sbomify.com/CVE-2019-20005/"}