{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1597 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1597 is a medium-severity vulnerability in Ibm Security Guardium, published on 17 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1597 and fix it if it is affected.\n\nWhat it is: CVE-2017-1597 is a medium-severity vulnerability in Ibm Security Guardium, published on 17 Dec 2018. 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-2017-1597 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-2017-1597/ (Markdown: https://insights.sbomify.com/CVE-2017-1597/index.md)","id":"CVE-2017-1597","markdown":"https://insights.sbomify.com/CVE-2017-1597/index.md","name":"CVE-2017-1597","record":{"aliases":["GHSA-64hv-cf4h-5rcx"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Database Activity Monitor","requires_auth":"none","summary":"IBM Security Guardium allows weak passwords by default, enabling attackers to compromise user accounts through brute-force or guessing attacks.","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":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/A:N/AC:H/AV:N/C:H/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"IBM Security Guardium 10.0, 10.0.1, 10.1, 10.1.2, 10.1.3, 10.1.4, and 10.5 Database Activity Monitor does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 132610.","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-2017-1597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_guardium","products":["ibm:security_guardium"],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Weak cryptography in Security Guardium","id":"CVE-2017-1598"},"packages":[],"prev":{"headline":"Information disclosure in Security Guardium","id":"CVE-2017-1596"},"products":["Security Guardium"],"published":"2018-12-17","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":"IBM Security Guardium allows weak passwords by default, enabling attackers to compromise user accounts through brute-force or guessing attacks.","url":"https://insights.sbomify.com/CVE-2017-1597/"}