{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-8776 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8776 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8776 is a high-severity vulnerability in n/a, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8776 and fix it if it is affected.\n\nWhat it is: CVE-2017-8776 is a high-severity vulnerability in n/a, published on 4 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-8776 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-2017-8776/ (Markdown: https://insights.sbomify.com/CVE-2017-8776/index.md)","id":"CVE-2017-8776","markdown":"https://insights.sbomify.com/CVE-2017-8776/index.md","name":"CVE-2017-8776","record":{"aliases":["GHSA-72r5-vfpw-765r"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Antivirus software","requires_auth":"none","summary":"Quick Heal security products lack ASLR and DEP protections in many binaries, facilitating memory corruption exploits and code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"antivirus_pro","vendor":"quickheal"},{"product":"internet_security","vendor":"quickheal"},{"product":"total_security","vendor":"quickheal"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Quick Heal Internet Security 10.1.0.316, Quick Heal Total Security 10.1.0.316, and Quick Heal AntiVirus Pro 10.1.0.316 have approximately 165 PE files in the default installation that do not use ASLR/DEP protection mechanisms that provide sufficient defense against directed attacks against the product.","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":"Security feature bypass in n/a","id":"CVE-2017-8776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2017-8777"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-8775"},"products":["n/a"],"published":"2017-05-04","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8773","kev_date_added":null,"published":"2017-05-04"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8774","kev_date_added":null,"published":"2017-05-04"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8775","kev_date_added":null,"published":"2017-05-04"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-5005","kev_date_added":null,"published":"2017-01-02"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2018-8090","kev_date_added":null,"published":"2018-07-25"},{"cvss_score":7.2,"headline":"Memory corruption in n/a","id":"CVE-2013-6767","kev_date_added":null,"published":"2013-12-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Quick Heal security products lack ASLR and DEP protections in many binaries, facilitating memory corruption exploits and code execution.","url":"https://insights.sbomify.com/CVE-2017-8776/"}