{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-20414 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-20414 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-20414 is a medium-severity denial of service vulnerability in IBM Guardium Data Encryption, published on 12 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-20414 and fix it if it is affected.\n\nWhat it is: CVE-2021-20414 is a medium-severity denial of service vulnerability in IBM Guardium Data Encryption, published on 12 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-20414 in the wild and no public exploit code.\n\nAffected product: IBM Guardium Data Encryption. 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-20414/ (Markdown: https://insights.sbomify.com/CVE-2021-20414/index.md)","id":"CVE-2021-20414","markdown":"https://insights.sbomify.com/CVE-2021-20414/index.md","name":"CVE-2021-20414","record":{"aliases":["GHSA-95w5-wfx4-75p8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Guardium Data Encryption","requires_auth":"high_privilege","summary":"Attackers can brute force sensitive information in IBM Guardium Data Encryption due to insufficient rate limiting on interactions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"guardium_data_encryption","vendor":"ibm"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/PR:H/I:N/C:H/AV:N/AC:H/S:U/UI:N/A:N/E:U/RL:O/RC:C","version":"3.0"},"cwes":[],"description":"IBM Guardium Data Encryption (GDE) 3.0.0.2 could allow a user to bruce force sensitive information due to not properly limiting the number of interactions. IBM X-Force ID: 196216.","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":"Denial of service in Guardium Data Encryption","id":"CVE-2021-20414","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Guardium Data Encryption","id":"CVE-2021-20415"},"packages":[],"prev":{"headline":"Information disclosure in Guardium Data Encryption","id":"CVE-2021-20413"},"products":["Guardium Data Encryption"],"published":"2021-07-12","related":[{"cvss_score":8.8,"headline":"Command injection in Security Guardium Data Encryption","id":"CVE-2019-4713","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":7.4,"headline":"Weak cryptography in Security Guardium Data Encryption","id":"CVE-2019-4698","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":6.8,"headline":"Hardcoded credentials in Security Guardium Data Encryption","id":"CVE-2019-4694","kev_date_added":null,"published":"2020-08-26"},{"cvss_score":6.5,"headline":"Missing authorization in Guardium Data Encryption","id":"CVE-2021-20474","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":6.3,"headline":"Auth bypass in Guardium Data Encryption","id":"CVE-2021-20378","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":6.2,"headline":"Other in Security Guardium Data Encryption","id":"CVE-2021-39022","kev_date_added":null,"published":"2022-03-10"},{"cvss_score":6,"headline":"Hardcoded credentials in Security Guardium Data Encryption","id":"CVE-2019-4693","kev_date_added":null,"published":"2020-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["IBM"]},"summary":"Attackers can brute force sensitive information in IBM Guardium Data Encryption due to insufficient rate limiting on interactions.","url":"https://insights.sbomify.com/CVE-2021-20414/"}