# CVE-2017-1269: SQL injection in Security Guardium

> A remote attacker can execute SQL injection attacks to view, add, modify, or delete database information in IBM Security Guardium.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-c642-9xqv-xjrx

## What is CVE-2017-1269?

CVE-2017-1269 is a critical SQL injection vulnerability in Ibm Security Guardium, published on 5 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Security Guardium 10.0 and 10.1 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-force ID: 124744

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-1269?

It affects 1 product.


Products: Ibm Security Guardium.

## How do I fix CVE-2017-1269?

No fix has been published for CVE-2017-1269 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-1269 being exploited?

There is no known exploitation of CVE-2017-1269 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Security Guardium

- [CVE-2023-35893](https://insights.sbomify.com/CVE-2023-35893/): IBM Security Guardium command execution (critical 9.9)
- [CVE-2017-1253](https://insights.sbomify.com/CVE-2017-1253/): Command injection in Security Guardium (critical 9.9)
- [CVE-2023-47709](https://insights.sbomify.com/CVE-2023-47709/): IBM Security Guardium command injection (critical 9.1)
- [CVE-2023-30435](https://insights.sbomify.com/CVE-2023-30435/): IBM Security Guardium cross-site scripting (high 8.9)
- [CVE-2020-4952](https://insights.sbomify.com/CVE-2020-4952/): Privilege escalation in Security Guardium (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1269 and fix it if it is affected.

What it is: CVE-2017-1269 is a critical SQL injection vulnerability in Ibm Security Guardium, published on 5 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1269 in the wild and no public exploit code.

Affected product: Ibm Security Guardium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1269/ (Markdown: https://insights.sbomify.com/CVE-2017-1269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1269
- OSV: https://osv.dev/vulnerability/CVE-2017-1269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1269/
Summaries are generated and may contain mistakes; the official description above is the record.