{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43099 is a medium-severity path traversal vulnerability in n/a, published on 28 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43099 and fix it if it is affected.\n\nWhat it is: CVE-2021-43099 is a medium-severity path traversal vulnerability in n/a, published on 28 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43099 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-2021-43099/ (Markdown: https://insights.sbomify.com/CVE-2021-43099/index.md)","id":"CVE-2021-43099","markdown":"https://insights.sbomify.com/CVE-2021-43099/index.md","name":"CVE-2021-43099","record":{"aliases":["GHSA-g5mc-2cpg-f638"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"bbs web application","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code by uploading a crafted zip file with directory traversal filenames during the upgrade process.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bbs","vendor":"diyhi"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An Archive Extraction (AKA \"Zip Slip) vulnerability exists in bbs 5.3 in the UpgradeNow function in UpgradeManageAction.java, which unzips the arbitrary upladed zip file without checking filenames. The vulnerability is exploited using a specially crafted archive that holds directory traversal filenames (e.g. ../../evil.exe).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in n/a","id":"CVE-2021-43099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2021-43100"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2021-43098"},"products":["n/a"],"published":"2022-03-28","related":[{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2021-43097","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2021-43098","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2021-43100","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2021-43101","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2021-43102","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2021-43103","kev_date_added":null,"published":"2022-03-28"},{"cvss_score":5.3,"headline":"diyhi bbs File Compression FilePackageManageAction.java information disclosure","id":"CVE-2025-9461","kev_date_added":null,"published":"2025-08-26"}],"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 execute arbitrary code by uploading a crafted zip file with directory traversal filenames during the upgrade process.","url":"https://insights.sbomify.com/CVE-2021-43099/"}