{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20019 is a medium-severity denial of service vulnerability in n/a, published on 27 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-20019 and fix it if it is affected.\n\nWhat it is: CVE-2019-20019 is a medium-severity denial of service vulnerability in n/a, published on 27 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-20019 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-20019/ (Markdown: https://insights.sbomify.com/CVE-2019-20019/index.md)","id":"CVE-2019-20019","markdown":"https://insights.sbomify.com/CVE-2019-20019/index.md","name":"CVE-2019-20019","record":{"aliases":["DEBIAN-CVE-2019-20019","GHSA-qvf4-mqvf-rprj","UBUNTU-CVE-2019-20019"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Matio library","requires_auth":"none","summary":"An attacker can cause a denial of service via excessive memory allocation in the Matio library when processing malicious MAT files.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"matio","vendor":"matio_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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"An attempted excessive memory allocation was discovered in Mat_VarRead5 in mat5.c in matio 1.5.17.","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":"Denial of service in n/a","id":"CVE-2019-20019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-20020"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-20018"},"products":["n/a"],"published":"2019-12-27","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9028","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9030","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9033","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9034","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9035","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2019-9037","kev_date_added":null,"published":"2019-02-23"},{"cvss_score":8.8,"headline":"Integer overflow in n/a","id":"CVE-2020-19497","kev_date_added":null,"published":"2021-07-21"}],"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 denial of service via excessive memory allocation in the Matio library when processing malicious MAT files.","url":"https://insights.sbomify.com/CVE-2019-20019/"}