{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29060 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29060 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29060 is a high-severity vulnerability in Fortinet FortiDDoS, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29060 and fix it if it is affected.\n\nWhat it is: CVE-2022-29060 is a high-severity vulnerability in Fortinet FortiDDoS, published on 18 Jul 2022. 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-2022-29060 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiDDoS. 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-2022-29060/ (Markdown: https://insights.sbomify.com/CVE-2022-29060/index.md)","id":"CVE-2022-29060","markdown":"https://insights.sbomify.com/CVE-2022-29060/index.md","name":"CVE-2022-29060","record":{"aliases":["GHSA-vgx6-62w9-6xwh"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FortiDDoS API","requires_auth":"none","summary":"An attacker can sign JWT tokens for any device by retrieving a hard-coded cryptographic key, bypassing authentication in FortiDDoS.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiddos","vendor":"fortinet"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:X/RL:U/RC:R","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"A use of hard-coded cryptographic key vulnerability [CWE-321] in FortiDDoS API 5.5.0 through 5.5.1, 5.4.0 through 5.4.2, 5.3.0 through 5.3.1, 5.2.0, 5.1.0 may allow an attacker who managed to retrieve the key from one device to sign JWT tokens for any device.","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":"Hardcoded credentials in Fortinet FortiDDoS","id":"CVE-2022-29060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Fortinet FortiSOAR","id":"CVE-2022-29061"},"packages":[],"prev":{"headline":"SQL injection in FortiWeb","id":"CVE-2022-29059"},"products":["Fortinet FortiDDoS"],"published":"2022-07-18","related":[{"cvss_score":5.9,"headline":"Command injection in FortiDDoS","id":"CVE-2022-27486","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":5,"headline":"Information disclosure in FortiDDoS","id":"CVE-2021-24008","kev_date_added":null,"published":"2025-03-28"}],"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 attacker can sign JWT tokens for any device by retrieving a hard-coded cryptographic key, bypassing authentication in FortiDDoS.","url":"https://insights.sbomify.com/CVE-2022-29060/"}