{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-43906 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-43906 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43906 is a low-severity vulnerability in Ibm Security Guardium, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-43906 and fix it if it is affected.\n\nWhat it is: CVE-2022-43906 is a low-severity vulnerability in Ibm Security Guardium, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-43906 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-2022-43906/ (Markdown: https://insights.sbomify.com/CVE-2022-43906/index.md)","id":"CVE-2022-43906","markdown":"https://insights.sbomify.com/CVE-2022-43906/index.md","name":"CVE-2022-43906","record":{"aliases":["GHSA-gwc8-2896-j47c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Guardium","requires_auth":"none","summary":"Attackers can access sensitive information due to missing SameSite cookie attributes in IBM Security Guardium.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_guardium","vendor":"ibm"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"IBM Security Guardium 11.5 could disclose sensitive information due to a missing or insecure SameSite attribute for a sensitive cookie.  IBM X-Force ID:  240897.","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":"IBM Security Guardium information disclosure","id":"CVE-2022-43906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_guardium","products":["ibm:security_guardium"],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Security Guardium command execution","id":"CVE-2022-43907"},"packages":[],"prev":{"headline":"IBM Security Guardium information disclosure","id":"CVE-2022-43904"},"products":["Security Guardium"],"published":"2023-10-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["IBM"]},"summary":"Attackers can access sensitive information due to missing SameSite cookie attributes in IBM Security Guardium.","url":"https://insights.sbomify.com/CVE-2022-43906/"}