{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4191 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4191 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4191 is a medium-severity vulnerability in Ibm Security Guardium, published on 4 Jun 2020. 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-2020-4191 and fix it if it is affected.\n\nWhat it is: CVE-2020-4191 is a medium-severity vulnerability in Ibm Security Guardium, published on 4 Jun 2020. 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-2020-4191 in the wild and no public exploit code.\n\nAffected product: Ibm Security Guardium. 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-2020-4191/ (Markdown: https://insights.sbomify.com/CVE-2020-4191/index.md)","id":"CVE-2020-4191","markdown":"https://insights.sbomify.com/CVE-2020-4191/index.md","name":"CVE-2020-4191","record":{"aliases":["GHSA-gvc8-7r7h-crrj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Security Guardium","requires_auth":"high_privilege","summary":"Weak cryptographic algorithms in IBM Security Guardium allow attackers to decrypt highly sensitive information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_guardium","vendor":"ibm"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.0/PR:H/UI:N/A:N/S:U/AC:H/I:N/AV:L/C:H/RL:O/RC:C/E:U","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM Security Guardium 11.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 174852.","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 Security Guardium","id":"CVE-2020-4191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_guardium","products":["ibm:security_guardium"],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Security Guardium","id":"CVE-2020-4193"},"packages":[],"prev":{"headline":"Hardcoded credentials in Security Guardium","id":"CVE-2020-4190"},"products":["Security Guardium"],"published":"2020-06-04","related":[{"cvss_score":9.9,"headline":"IBM Security Guardium command execution","id":"CVE-2023-35893","kev_date_added":null,"published":"2023-08-16"},{"cvss_score":9.9,"headline":"Command injection in Security Guardium","id":"CVE-2017-1253","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":9.8,"headline":"SQL injection in Security Guardium","id":"CVE-2017-1269","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":9.1,"headline":"IBM Security Guardium command injection","id":"CVE-2023-47709","kev_date_added":null,"published":"2024-05-11"},{"cvss_score":8.9,"headline":"IBM Security Guardium cross-site scripting","id":"CVE-2023-30435","kev_date_added":null,"published":"2023-08-27"},{"cvss_score":8.8,"headline":"Privilege escalation in Security Guardium","id":"CVE-2020-4952","kev_date_added":null,"published":"2021-01-27"},{"cvss_score":8.8,"headline":"Command injection in Security Guardium","id":"CVE-2020-4180","kev_date_added":null,"published":"2020-06-03"}],"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":"Weak cryptographic algorithms in IBM Security Guardium allow attackers to decrypt highly sensitive information.","url":"https://insights.sbomify.com/CVE-2020-4191/"}