{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-0249 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0249 is a high-severity SQL injection vulnerability in Ibm Security Guardium, published on 16 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-0249 and fix it if it is affected.\n\nWhat it is: CVE-2016-0249 is a high-severity SQL injection vulnerability in Ibm Security Guardium, published on 16 Oct 2016. 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-2016-0249 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-2016-0249/ (Markdown: https://insights.sbomify.com/CVE-2016-0249/index.md)","id":"CVE-2016-0249","markdown":"https://insights.sbomify.com/CVE-2016-0249/index.md","name":"CVE-2016-0249","record":{"aliases":["GHSA-rrh9-jpqp-xx8r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Database Activity Monitor","requires_auth":"none","summary":"Remote attackers can execute arbitrary SQL commands in IBM Security Guardium Database Activity Monitor, potentially compromising database integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_guardium","vendor":"ibm"}],"cvss":{"score":8.6,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1 before p100 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.","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":"SQL injection in n/a","id":"CVE-2016-0249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_guardium","products":["ibm:security_guardium"],"type":"sql_injection","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2016-0250"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2016-0248"},"products":["n/a"],"published":"2016-10-16","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-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary SQL commands in IBM Security Guardium Database Activity Monitor, potentially compromising database integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2016-0249/"}