{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10861 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10861 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10861 is a high-severity path traversal vulnerability in n/a, published on 1 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10861 and fix it if it is affected.\n\nWhat it is: CVE-2020-10861 is a high-severity path traversal vulnerability in n/a, published on 1 Apr 2020. 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-2020-10861 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-10861/ (Markdown: https://insights.sbomify.com/CVE-2020-10861/index.md)","id":"CVE-2020-10861","markdown":"https://insights.sbomify.com/CVE-2020-10861/index.md","name":"CVE-2020-10861","record":{"aliases":["GHSA-f539-gp43-69fv"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Avast Antivirus","requires_auth":"none","summary":"Attackers can delete arbitrary files from the Avast program path via RPC, bypassing Self Defense protections in Avast Antivirus.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"antivirus","vendor":"avast"}],"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":"An issue was discovered in Avast Antivirus before 20. The aswTask RPC endpoint for the TaskEx library in the Avast Service (AvastSvc.exe) allows attackers to achieve Arbitrary File Deletion from Avast Program Path via RPC, when Self Defense is Enabled.","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":"Path traversal in n/a","id":"CVE-2020-10861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-10862"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-10860"},"products":["n/a"],"published":"2020-04-01","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.8,"headline":"Missing authorization in n/a","id":"CVE-2017-8307","kev_date_added":null,"published":"2017-04-27"},{"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-04","vendors":["n/a"]},"summary":"Attackers can delete arbitrary files from the Avast program path via RPC, bypassing Self Defense protections in Avast Antivirus.","url":"https://insights.sbomify.com/CVE-2020-10861/"}