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

> Remote attackers can execute arbitrary SQL commands via the id parameter in the where method, potentially compromising data integrity and confidentiality.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 29 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-17917, GHSA-vqpc-h5g8-fhrw

## What is CVE-2017-17917?

CVE-2017-17917 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the 'where' method in Ruby on Rails 5.1.4 and earlier allows remote attackers to execute arbitrary SQL commands via the 'id' parameter. NOTE: The vendor disputes this issue because the documentation states that this method is not intended for use with untrusted input

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

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

It affects 1 product.


Products: Rubyonrails Rails.

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

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

## Is CVE-2017-17917 being exploited?

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

Public exploit code:

- https://github.com/matiasarenhard/rails-cve-2017-17917 (github_poc): https://github.com/matiasarenhard/rails-cve-2017-17917

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)
- [CVE-2023-22792](https://insights.sbomify.com/CVE-2023-22792/): ReDoS based DoS vulnerability in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17917 is a high-severity SQL injection vulnerability in Rubyonrails Rails, published on 29 Dec 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-17917 in the wild and no public exploit code.

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

## Sources

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

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