CVE-2017-17916

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
71.7%
KEV
Not listed

Published

December 29, 2017

Last Modified

May 13, 2026

Frequently asked(5)

What is CVE-2017-17916?
CVE-2017-17916 is a high vulnerability published on December 29, 2017. SQL injection vulnerability in the 'find_by' method in Ruby on Rails 5.1.4 and earlier allows remote attackers to execute arbitrary SQL commands via the 'name' parameter. NOTE: The vendor disputes this issue because the documentation states that this method is not intended for use with untrusted…
When was CVE-2017-17916 disclosed?
CVE-2017-17916 was first published in the National Vulnerability Database on December 29, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17916 actively exploited?
CVE-2017-17916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-17916?
CVE-2017-17916 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2017-17916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-17916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-17916

Explore →

Is Your Infrastructure Affected by CVE-2017-17916?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.