{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8307 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8307 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8307 is a critical missing authorization vulnerability in n/a, published on 27 Apr 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-8307 and fix it if it is affected.\n\nWhat it is: CVE-2017-8307 is a critical missing authorization vulnerability in n/a, published on 27 Apr 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-8307 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-8307/ (Markdown: https://insights.sbomify.com/CVE-2017-8307/index.md)","id":"CVE-2017-8307","markdown":"https://insights.sbomify.com/CVE-2017-8307/index.md","name":"CVE-2017-8307","record":{"aliases":["GHSA-7gqh-6434-f3jx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Avast Antivirus","requires_auth":"none","summary":"Unprivileged users can launch binaries or modify files via the Avast service API when Self-Defense is disabled, enabling DoS or evidence tampering.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"antivirus","vendor":"avast"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"In Avast Antivirus before v17, using the LPC interface API exposed by the AvastSVC.exe Windows service, it is possible to launch predefined binaries, or replace or delete arbitrary files. This vulnerability is exploitable by any unprivileged user when Avast Self-Defense is disabled. It is also exploitable in conjunction with CVE-2017-8308 when Avast Self-Defense is enabled. The vulnerability allows for Denial of Service attacks and hiding traces of a possible attack.","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":"Missing authorization in n/a","id":"CVE-2017-8307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-8308"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-8305"},"products":["n/a"],"published":"2017-04-27","related":[{"cvss_score":9.9,"headline":"Race condition in (Free/Inernet Security/Ultimate) Antivirus","id":"CVE-2025-13032","kev_date_added":null,"published":"2025-11-11"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-10867","kev_date_added":null,"published":"2020-04-01"},{"cvss_score":9,"headline":"Integer Overflow in Avast Antiviurs 25.1.981.6 on Windows may result in privilege escalation","id":"CVE-2025-3500","kev_date_added":null,"published":"2025-12-01"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2021-45335","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.8,"headline":"Privilege escalation vulnerability in the Sandbox component of Avast Antivirus prior to 20.4 allows a local sandboxed code to gain elevated","id":"CVE-2021-45336","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-45337","kev_date_added":null,"published":"2021-12-27"}],"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-05","vendors":["n/a"]},"summary":"Unprivileged users can launch binaries or modify files via the Avast service API when Self-Defense is disabled, enabling DoS or evidence tampering.","url":"https://insights.sbomify.com/CVE-2017-8307/"}