Skip to content

Recurly gem Server-Side Request Forgery in Resource#find method

Critical severity GitHub Reviewed Published Dec 6, 2017 to the GitHub Advisory Database • Updated Aug 29, 2023

Package

bundler recurly (RubyGems)

Affected versions

>= 2.11.0, < 2.11.3
>= 2.10.0, < 2.10.4
>= 2.9.0, < 2.9.2
>= 2.8.0, < 2.8.2
>= 2.7.0, < 2.7.8
>= 2.6.0, < 2.6.3
>= 2.5.0, < 2.5.4
>= 2.4.0, < 2.4.11
>= 2.3.0, < 2.3.10
>= 2.2.0, < 2.2.5
>= 2.1.0, < 2.1.11
>= 2.0.0, < 2.0.13

Patched versions

2.11.3
2.10.4
2.9.2
2.8.2
2.7.8
2.6.3
2.5.4
2.4.11
2.3.10
2.2.5
2.1.11
2.0.13

Description

The Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3 is vulnerable to a Server-Side Request Forgery vulnerability in the Resource#find method that could result in compromise of API keys or other critical resources.

References

Published to the GitHub Advisory Database Dec 6, 2017
Reviewed Jun 16, 2020
Last updated Aug 29, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.377%
(73rd percentile)

Weaknesses

CVE ID

CVE-2017-0905

GHSA ID

GHSA-x27v-x225-gq8g

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.