{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-19513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-19513 is a high-severity memory corruption vulnerability in n/a, published on 18 Feb 2021. 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-2020-19513 and fix it if it is affected.\n\nWhat it is: CVE-2020-19513 is a high-severity memory corruption vulnerability in n/a, published on 18 Feb 2021. 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-2020-19513 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-2020-19513/ (Markdown: https://insights.sbomify.com/CVE-2020-19513/index.md)","id":"CVE-2020-19513","markdown":"https://insights.sbomify.com/CVE-2020-19513/index.md","name":"CVE-2020-19513","record":{"aliases":["GHSA-7fxq-f8vg-7f3w"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"System information tool","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code via a buffer overflow in AIDA64 Engineer by crafting input that overwrites the SEH handler.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"aida64","vendor":"aida64"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Buffer overflow in FinalWire Ltd AIDA64 Engineer 6.00.5100 allows attackers to execute arbitrary code by creating a crafted input that will overwrite the SEH handler.","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":"Memory corruption in n/a","id":"CVE-2020-19513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-19515"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-19511"},"products":["n/a"],"published":"2021-02-18","related":[{"cvss_score":8.6,"headline":"AIDA64 Extreme 5.99.4900 SEH Buffer Overflow via Logging","id":"CVE-2019-25629","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.6,"headline":"AIDA64 Business 5.99.4900 SEH Buffer Overflow via EggHunter","id":"CVE-2019-25631","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.6,"headline":"AIDA64 Extreme 5.99.4900 SEH Buffer Overflow via EggHunter","id":"CVE-2019-25633","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.4,"headline":"Aida64 6.10.5200 - Buffer Overflow","id":"CVE-2019-25360","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2019-7244","kev_date_added":null,"published":"2020-03-25"},{"cvss_score":4.6,"headline":"Everest 5.50.2100 - 'Open File' Denial of Service","id":"CVE-2020-37140","kev_date_added":null,"published":"2026-02-05"}],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via a buffer overflow in AIDA64 Engineer by crafting input that overwrites the SEH handler.","url":"https://insights.sbomify.com/CVE-2020-19513/"}