{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-23005 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-23005 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-23005 is a critical vulnerability in F5 Big-Iq Centralized Management, published on 31 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-23005 and fix it if it is affected.\n\nWhat it is: CVE-2021-23005 is a critical vulnerability in F5 Big-Iq Centralized Management, published on 31 Mar 2021. 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-2021-23005 in the wild and no public exploit code.\n\nAffected product: F5 Big-Iq Centralized Management. 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-23005/ (Markdown: https://insights.sbomify.com/CVE-2021-23005/index.md)","id":"CVE-2021-23005","markdown":"https://insights.sbomify.com/CVE-2021-23005/index.md","name":"CVE-2021-23005","record":{"aliases":["GHSA-x5xq-4c5q-64fh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"BIG-IQ management platform","requires_auth":"none","summary":"Attackers can intercept high-availability failover traffic because BIG-IQ fails to use TLS for Corosync when a Quorum device is configured.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"big-iq_centralized_management","vendor":"f5"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[],"description":"On all 7.x and 6.x versions (fixed in 8.0.0), when using a Quorum device for BIG-IQ high availability (HA) for automatic failover, BIG-IQ does not make use of Transport Layer Security (TLS) with the Corosync protocol. Note: Software versions which have reached End of Software Development (EoSD) are not evaluated.","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":"Weak cryptography in BIG-IQ","id":"CVE-2021-23005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"f5:big-iq_centralized_management","products":["f5:big-iq_centralized_management"],"type":"weak_cryptography","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"On all 7.x and 6.x versions (fixed in 8.0.0), undisclosed BIG-IQ pages have a reflected cross-site scripting vulnerability.","id":"CVE-2021-23006"},"packages":[],"prev":{"headline":"Misconfiguration in BIG-IP","id":"CVE-2021-23004"},"products":["BIG-IQ"],"published":"2021-03-31","related":[{"cvss_score":9.8,"headline":"Command injection in BIG-IQ","id":"CVE-2020-5868","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":9.1,"headline":"Information disclosure in BIG-IQ","id":"CVE-2020-5869","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.1,"headline":"Missing authorization in BIG-IQ","id":"CVE-2020-5870","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":7.5,"headline":"Missing authorization in BIG-IQ","id":"CVE-2021-22995","kev_date_added":null,"published":"2021-03-31"},{"cvss_score":7.5,"headline":"Denial of service in BIG-IQ","id":"CVE-2021-22996","kev_date_added":null,"published":"2021-03-31"},{"cvss_score":7.5,"headline":"Missing authorization in BIG-IQ","id":"CVE-2021-22997","kev_date_added":null,"published":"2021-03-31"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can intercept high-availability failover traffic because BIG-IQ fails to use TLS for Corosync when a Quorum device is configured.","url":"https://insights.sbomify.com/CVE-2021-23005/"}