{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-0864 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-0864 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-0864 is a medium-severity denial of service vulnerability in Microsoft .Net Framework, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-0864 and fix it if it is affected.\n\nWhat it is: CVE-2019-0864 is a medium-severity denial of service vulnerability in Microsoft .Net Framework, published on 16 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-0864 in the wild and no public exploit code.\n\nAffected product: Microsoft .Net Framework. 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-0864/ (Markdown: https://insights.sbomify.com/CVE-2019-0864/index.md)","id":"CVE-2019-0864","markdown":"https://insights.sbomify.com/CVE-2019-0864/index.md","name":"CVE-2019-0864","record":{"aliases":["GHSA-prjj-r5f6-p9xf"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":".NET Framework","requires_auth":"low_privilege","summary":"Attackers can cause a denial of service by exploiting improper heap memory handling in the .NET Framework.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":".net_framework","vendor":"microsoft"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"A denial of service vulnerability exists when .NET Framework improperly handles objects in heap memory, aka '.NET Framework Denial of Service Vulnerability'.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in Microsoft .NET Framework 2.0","id":"CVE-2019-0864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:.net_framework","products":["microsoft:.net_framework"],"type":"denial_of_service","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Windows","id":"CVE-2019-0865"},"packages":[],"prev":{"headline":"Microsoft Windows Error Reporting (WER) Privilege Escalation","id":"CVE-2019-0863"},"products":["Microsoft .NET Framework 2.0","Microsoft .NET Framework 3.0","Microsoft .NET Framework 3.5","Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for 32-bit Systems","Microsoft .NET Framework 3.5 on Windows 10 Version 1903 for x64-based Systems","Microsoft .NET Framework 3.5 on Windows Server, version 1903 (Server Core installation)","Microsoft .NET Framework 3.5.1","Microsoft .NET Framework 4.5.2","Microsoft .NET Framework 4.6","Microsoft .NET Framework 4.6.2 on Windows 10 for 32-bit Systems","Microsoft .NET Framework 4.6.2 on Windows 10 for x64-based Systems","Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2","Microsoft .NET Framework 4.6/4.6.1/4.6.2/4.7/4.7.1/4.7.2","Microsoft .NET Framework 4.7.1/4.7.2","Microsoft .NET Framework 4.7.2","Microsoft .NET Framework 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems","Microsoft .NET Framework 4.7/4.7.1/4.7.2","Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1703 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1703 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1709 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1803 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1809 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1809 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1903 for 32-bit Systems","Microsoft .NET Framework 4.8 on Windows 10 Version 1903 for x64-based Systems","Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1","Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1","Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systems","Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systems","Microsoft .NET Framework 4.8 on Windows RT 8.1","Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1","Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)","Microsoft .NET Framework 4.8 on Windows Server 2012","Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)","Microsoft .NET Framework 4.8 on Windows Server 2012 R2","Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)","Microsoft .NET Framework 4.8 on Windows Server 2016","Microsoft .NET Framework 4.8 on Windows Server 2016  (Server Core installation)","Microsoft .NET Framework 4.8 on Windows Server 2019","Microsoft .NET Framework 4.8 on Windows Server 2019  (Server Core installation)","Microsoft .NET Framework 4.8 on Windows Server, version 1803  (Server Core Installation)","Microsoft .NET Framework 4.8 on Windows Server, version 1903 (Server Core installation)"],"published":"2019-05-16","related":[{"cvss_score":9.8,"headline":"Microsoft .NET Framework Remote Code Execution","id":"CVE-2020-0646","kev_date_added":"2021-11-03","published":"2020-01-14"},{"cvss_score":7.8,"headline":"Microsoft .NET Framework Remote Code Execution","id":"CVE-2017-8759","kev_date_added":"2021-11-03","published":"2017-09-13"},{"cvss_score":7.8,"headline":"Microsoft Windows Remote Code Execution","id":"CVE-2015-1671","kev_date_added":"2022-05-25","published":"2015-05-13"},{"cvss_score":7.5,"headline":"Microsoft .NET Framework Information Disclosure","id":"CVE-2024-29059","kev_date_added":"2025-02-04","published":"2024-03-22"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2014-4073","kev_date_added":null,"published":"2014-10-15"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-4121","kev_date_added":null,"published":"2014-10-15"},{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2014-1806","kev_date_added":null,"published":"2014-05-14"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Microsoft"]},"summary":"Attackers can cause a denial of service by exploiting improper heap memory handling in the .NET Framework.","url":"https://insights.sbomify.com/CVE-2019-0864/"}