{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-42004 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-42004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-42004 is a high-severity code injection vulnerability in Ibm Security Guardium, published on 28 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-42004 and fix it if it is affected.\n\nWhat it is: CVE-2023-42004 is a high-severity code injection vulnerability in Ibm Security Guardium, published on 28 Nov 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-42004 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-2023-42004/ (Markdown: https://insights.sbomify.com/CVE-2023-42004/index.md)","id":"CVE-2023-42004","markdown":"https://insights.sbomify.com/CVE-2023-42004/index.md","name":"CVE-2023-42004","record":{"aliases":["GHSA-3g3f-pff6-g3m3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Security Guardium","requires_auth":"low_privilege","summary":"Remote attackers can execute malicious commands via CSV injection in IBM Security Guardium due to improper validation of file contents.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_guardium","vendor":"ibm"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"IBM Security Guardium 11.3, 11.4, and 11.5 is potentially vulnerable to CSV injection.  A remote attacker could execute malicious commands due to improper validation of csv file contents.  IBM X-Force ID:  265262.","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 CSV injection","id":"CVE-2023-42004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_guardium","products":["ibm:security_guardium"],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Db2 on Cloud Pak for Data privilege escalation","id":"CVE-2023-42005"},"packages":[],"prev":{"headline":"Arcserve UDP Agent Unauthenticated Path Traversal File Upload","id":"CVE-2023-42000"},"products":["Security Guardium"],"published":"2023-11-28","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-11-21","vendors":["IBM"]},"summary":"Remote attackers can execute malicious commands via CSV injection in IBM Security Guardium due to improper validation of file contents.","url":"https://insights.sbomify.com/CVE-2023-42004/"}