{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-4686 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4686 is a low-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-4686 and fix it if it is affected.\n\nWhat it is: CVE-2019-4686 is a low-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-4686 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-4686/ (Markdown: https://insights.sbomify.com/CVE-2019-4686/index.md)","id":"CVE-2019-4686","markdown":"https://insights.sbomify.com/CVE-2019-4686/index.md","name":"CVE-2019-4686","record":{"aliases":["GHSA-r4j3-mhcf-4v9x"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Guardium Data Encryption","requires_auth":"none","summary":"Attackers can steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Security 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":3.7,"severity":"low","source":"cna","vector":"CVSS:3.0/A:N/UI:N/C:L/I:N/PR:N/AC:H/S:U/AV:N/RC:C/RL:O/E:U","version":"3.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"IBM Security Guardium Data Encryption (GDE) 3.0.0.2 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic. IBM X-Force ID: 171822.","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-4686","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":"Information disclosure in Security Guardium Data Encryption","id":"CVE-2019-4687"},"packages":[],"prev":{"headline":"Cross-site scripting in Tivoli Netcool Impact","id":"CVE-2019-4681"},"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":"Attackers can steal session cookies via insecure HTTP links, potentially leading to account takeover in IBM Security Guardium Data Encryption.","url":"https://insights.sbomify.com/CVE-2019-4686/"}