Ruby on Rails up to 5.1.4 where ID sql injection ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Ruby on Rails up to 5.1.4 and classified as critical. Affected by this vulnerability is the function where. Performing a manipulation of the argument ID as part of Parameter results in sql injection.
This vulnerability is reported as CVE-2017-17917. The attack is possible to be carried out remotely. No exploit exists.
The presence of this vulnerability remains uncertain at this time.
Details
A vulnerability classified as critical has been found in Ruby on Rails up to 5.1.4 (Programming Language Software). This affects the function where. The manipulation of the argument id as part of a Parameter leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The bug was discovered 12/27/2017. The weakness was disclosed 12/29/2017 (Website). The advisory is shared at kay-malwarebenchmark.github.io. This vulnerability is uniquely identified as CVE-2017-17917 since 12/26/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 232046 (Linux Distros Unpatched Vulnerability : CVE-2017-17917), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (232046). The entries VDB-111176, VDB-111178 and VDB-111179 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 232046
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2017-17917
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/26/2017 🔍12/27/2017 🔍
12/29/2017 🔍
12/29/2017 🔍
12/30/2017 🔍
03/07/2025 🔍
Sources
Advisory: kay-malwarebenchmark.github.ioStatus: Not defined
Disputed: 🔍
CVE: CVE-2017-17917 (🔍)
GCVE (CVE): GCVE-0-2017-17917
GCVE (VulDB): GCVE-100-111177
See also: 🔍
Entry
Created: 12/30/2017 11:57Updated: 03/07/2025 10:47
Changes: 12/30/2017 11:57 (59), 12/18/2019 16:06 (1), 06/27/2024 01:16 (17), 08/06/2024 01:26 (2), 03/07/2025 10:47 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.