# CVE-2017-11184: SQL injection in n/a

> An attacker can execute arbitrary SQL commands via the start parameter in GLPI, potentially reading or modifying database contents.

- **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:** Yes
- **Published:** 28 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-65r8-7pw5-7mrj, UBUNTU-CVE-2017-11184

## What is CVE-2017-11184?

CVE-2017-11184 is a critical SQL injection vulnerability in Glpi-Project Glpi, published on 28 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection exists in front/devicesoundcard.php in GLPI before 9.1.5 via the start parameter.

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

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

It affects 1 product.


Products: Glpi-Project Glpi.

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

Upgrade to a fixed version.

## Is CVE-2017-11184 being exploited?

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

## Other vulnerabilities in Glpi-Project Glpi

- [CVE-2022-35914](https://insights.sbomify.com/CVE-2022-35914/): Teclib GLPI Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-42802](https://insights.sbomify.com/CVE-2023-42802/): GLPI vulnerable to unallowed PHP script execution (critical 10.0)
- [CVE-2023-28849](https://insights.sbomify.com/CVE-2023-28849/): GLPI vulnerable to SQL injection and Stored XSS via inventory agent request (critical 10.0)
- [CVE-2022-35947](https://insights.sbomify.com/CVE-2022-35947/): SQL injection in GLPI (critical 10.0)
- [CVE-2022-31056](https://insights.sbomify.com/CVE-2022-31056/): SQL injection with _actor parameter in GLPI (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11184 is a critical SQL injection vulnerability in Glpi-Project Glpi, published on 28 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-11184 in the wild and no public exploit code.

Affected product: Glpi-Project Glpi. 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-11184/ (Markdown: https://insights.sbomify.com/CVE-2017-11184/index.md)
```

## Sources

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

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