{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-21526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-21526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-21526 is a critical path traversal vulnerability in n/a, published on 30 Sep 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-21526 and fix it if it is affected.\n\nWhat it is: CVE-2020-21526 is a critical path traversal vulnerability in n/a, published on 30 Sep 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-21526 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-21526/ (Markdown: https://insights.sbomify.com/CVE-2020-21526/index.md)","id":"CVE-2020-21526","markdown":"https://insights.sbomify.com/CVE-2020-21526/index.md","name":"CVE-2020-21526","record":{"aliases":["GHSA-44fm-5g3x-mp3f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Halo blog platform","requires_auth":"none","summary":"Attackers can bypass directory traversal checks to write arbitrary files, potentially leading to code execution on 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":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An Arbitrary file writing vulnerability in halo v1.1.3. In an interface to write files in the background, a directory traversal check is performed on the input path parameter, but the startsWith function can be used to bypass it.","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-21526","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":"Path traversal in n/a","id":"CVE-2020-21527"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-21525"},"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.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":"Attackers can bypass directory traversal checks to write arbitrary files, potentially leading to code execution on the Halo blog platform.","url":"https://insights.sbomify.com/CVE-2020-21526/"}