{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-29699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-29699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-29699 is a medium-severity vulnerability in Ibm Security Verify Access, published on 15 Jul 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-29699 and fix it if it is affected.\n\nWhat it is: CVE-2021-29699 is a medium-severity vulnerability in Ibm Security Verify Access, published on 15 Jul 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-29699 in the wild and no public exploit code.\n\nAffected product: Ibm Security Verify Access. 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-29699/ (Markdown: https://insights.sbomify.com/CVE-2021-29699/index.md)","id":"CVE-2021-29699","markdown":"https://insights.sbomify.com/CVE-2021-29699/index.md","name":"CVE-2021-29699","record":{"aliases":["GHSA-4g23-p4cm-hwrj"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Security Verify Access","requires_auth":"high_privilege","summary":"Remote privileged users can upload dangerous files in IBM Security Verify Access Docker, potentially leading to code execution.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_access","vendor":"ibm"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:A/A:H/AC:L/S:U/I:H/C:H/UI:R/PR:H/RC:C/E:U/RL:O","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"IBM Security Verify Access Docker 10.0.0 could allow a remote priviled user to upload arbitrary files with a dangerous file type that could be excuted by an user. IBM X-Force ID: 200600.","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":"File upload in Security Verify Access Docker","id":"CVE-2021-29699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_verify_access","products":["ibm:security_verify_access"],"type":"file_upload","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Sterling B2B Integrator","id":"CVE-2021-29700"},"packages":[],"prev":{"headline":"Information disclosure in Cloud Pak for Security","id":"CVE-2021-29697"},"products":["Security Verify Access Docker"],"published":"2021-07-15","related":[{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78401","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78406","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"IBM Security Verify Access Appliance command execution","id":"CVE-2024-49803","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-39070","kev_date_added":null,"published":"2022-02-02"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49805","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49806","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.3,"headline":"Security Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-1346","kev_date_added":null,"published":"2026-04-08"}],"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-09-16","vendors":["IBM"]},"summary":"Remote privileged users can upload dangerous files in IBM Security Verify Access Docker, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2021-29699/"}