{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-4689 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4689 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4689 is a medium-severity vulnerability in IBM Security Guardium Data Encryption, published on 26 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-4689 and fix it if it is affected.\n\nWhat it is: CVE-2019-4689 is a medium-severity vulnerability in IBM Security Guardium Data Encryption, published on 26 Aug 2020. 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-2019-4689 in the wild and no public exploit code.\n\nAffected product: IBM Security 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-2019-4689/ (Markdown: https://insights.sbomify.com/CVE-2019-4689/index.md)","id":"CVE-2019-4689","markdown":"https://insights.sbomify.com/CVE-2019-4689/index.md","name":"CVE-2019-4689","record":{"aliases":["GHSA-v98q-qcwf-wwvr"],"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":"none","summary":"Remote attackers can intercept sensitive data via man-in-the-middle attacks due to missing HTTP Strict Transport Security in IBM Guardium Data Encryption.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"guardium_data_encryption","vendor":"ibm"},{"product":"guardium_for_cloud_key_management","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/S:U/AC:H/PR:N/I:N/C:H/UI:N/A:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"IBM Security Guardium Data Encryption (GDE) 3.0.0.2 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 171826.","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":"Information disclosure in Security Guardium Data Encryption","id":"CVE-2019-4689","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Security Guardium Data Encryption","id":"CVE-2019-4691"},"packages":[],"prev":{"headline":"Information disclosure in Security Guardium Data Encryption","id":"CVE-2019-4688"},"products":["Security Guardium Data Encryption"],"published":"2020-08-26","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":"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":"Remote attackers can intercept sensitive data via man-in-the-middle attacks due to missing HTTP Strict Transport Security in IBM Guardium Data Encryption.","url":"https://insights.sbomify.com/CVE-2019-4689/"}