{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22130 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22130 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22130 is a medium-severity memory corruption vulnerability in Fortinet Fortiproxy, published on 3 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-22130 and fix it if it is affected.\n\nWhat it is: CVE-2021-22130 is a medium-severity memory corruption vulnerability in Fortinet Fortiproxy, published on 3 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-22130 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortiproxy. 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-22130/ (Markdown: https://insights.sbomify.com/CVE-2021-22130/index.md)","id":"CVE-2021-22130","markdown":"https://insights.sbomify.com/CVE-2021-22130/index.md","name":"CVE-2021-22130","record":{"aliases":["GHSA-r6h6-26c6-pwfv"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fortinet FortiProxy","requires_auth":"high_privilege","summary":"An authenticated remote attacker can cause a denial of service in FortiProxy by triggering a stack-based buffer overflow via a large cpuset mask value.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiproxy","vendor":"fortinet"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"A stack-based buffer overflow vulnerability in FortiProxy physical appliance CLI 2.0.0 to 2.0.1, 1.2.0 to 1.2.9, 1.1.0 to 1.1.6, 1.0.0 to 1.0.7 may allow an authenticated, remote attacker to perform a Denial of Service attack by running the `diagnose sys cpuset` with a large cpuset mask value. Fortinet is not aware of any successful exploitation of this vulnerability that would lead to code execution.","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":"Memory corruption in Fortinet FortiProxy","id":"CVE-2021-22130","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortiproxy","products":["fortinet:fortiproxy"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Weak cryptography in Fortinet FortiTokenAndroid, Fortinet FortiTokeniOS, Fortinet FortiTokenWinApp","id":"CVE-2021-22131"},"packages":[],"prev":{"headline":"Memory corruption in Fortinet FortiMail","id":"CVE-2021-22129"},"products":["Fortinet FortiProxy"],"published":"2021-06-03","related":[{"cvss_score":9.3,"headline":"Missing authorization in FortiPresence","id":"CVE-2022-41331","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.1,"headline":"Missing authorization in Fortinet FortiProxy","id":"CVE-2021-22128","kev_date_added":null,"published":"2021-03-04"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Fortinet"]},"summary":"An authenticated remote attacker can cause a denial of service in FortiProxy by triggering a stack-based buffer overflow via a large cpuset mask value.","url":"https://insights.sbomify.com/CVE-2021-22130/"}