{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-21527 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-21527 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-21527 is a high-severity path traversal vulnerability in n/a, published on 30 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-21527 and fix it if it is affected.\n\nWhat it is: CVE-2020-21527 is a high-severity path traversal vulnerability in n/a, published on 30 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-21527 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-21527/ (Markdown: https://insights.sbomify.com/CVE-2020-21527/index.md)","id":"CVE-2020-21527","markdown":"https://insights.sbomify.com/CVE-2020-21527/index.md","name":"CVE-2020-21527","record":{"aliases":["GHSA-v2gh-h86w-h9rq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Halo blog platform","requires_auth":"low_privilege","summary":"An attacker can delete arbitrary files on the server via directory traversal in the backup deletion function of the Halo blog platform.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"halo","vendor":"halo"}],"cvss":{"score":7.7,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"There is an Arbitrary file deletion vulnerability in halo v1.1.3. A backup function in the background allows a user, when deleting their backup files, to delete any files on the system through directory traversal.","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-21527","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-21528"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-21526"},"products":["n/a"],"published":"2020-09-30","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-32994","kev_date_added":null,"published":"2022-06-27"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-32995","kev_date_added":null,"published":"2022-06-27"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-18980","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-21522","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-21523","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-21526","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2025-44594","kev_date_added":null,"published":"2025-09-09"}],"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":"An attacker can delete arbitrary files on the server via directory traversal in the backup deletion function of the Halo blog platform.","url":"https://insights.sbomify.com/CVE-2020-21527/"}