CVE-2017-0905 - Server-Side Request Forgery (SSRF)

Severity

75%

Complexity

99%

Confidentiality

106%

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.

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.

CVSS 3.0 Base Score 9.8. CVSS Attack Vector: network. CVSS Attack Complexity: low. CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

CVSS 2.0 Base Score 7.5. CVSS Attack Vector: network. CVSS Attack Complexity: low. CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:P/A:P).

Overview

Type

Recurly Client Ruby

First reported 7 years ago

2017-11-13 17:29:00

Last updated 5 years ago

2019-10-09 23:21:00

Affected Software

Recurly Client Ruby 2.0.0

2.0.0

Recurly Client Ruby 2.0.1

2.0.1

Recurly Client Ruby 2.0.2

2.0.2

Recurly Client Ruby 2.0.3

2.0.3

Recurly Client Ruby 2.0.4

2.0.4

Recurly Client Ruby 2.0.5

2.0.5

Recurly Client Ruby 2.0.6

2.0.6

Recurly Client Ruby 2.0.7

2.0.7

Recurly Client Ruby 2.0.8

2.0.8

Recurly Client Ruby 2.0.9

2.0.9

Recurly Client Ruby 2.0.10

2.0.10

Recurly Client Ruby 2.0.11

2.0.11

Recurly Client Ruby 2.0.12

2.0.12

Recurly Client Ruby 2.1.0

2.1.0

Recurly Client Ruby 2.1.0 C

2.1.0

Recurly Client Ruby 2.1.1

2.1.1

Recurly Client Ruby 2.1.2

2.1.2

Recurly Client Ruby 2.1.3

2.1.3

Recurly Client Ruby 2.1.4

2.1.4

Recurly Client Ruby 2.1.5

2.1.5

Recurly Client Ruby 2.1.6

2.1.6

Recurly Client Ruby 2.1.7

2.1.7

Recurly Client Ruby 2.1.8

2.1.8

Recurly Client Ruby 2.1.9

2.1.9

Recurly Client Ruby 2.1.10

2.1.10

Recurly Client Ruby 2.2.0

2.2.0

Recurly Client Ruby 2.2.1

2.2.1

Recurly Client Ruby 2.2.2

2.2.2

Recurly Client Ruby 2.2.3

2.2.3

Recurly Client Ruby 2.2.4

2.2.4

Recurly Client Ruby 2.3.0

2.3.0

Recurly Client Ruby 2.3.0 Beta1

2.3.0

Recurly Client Ruby 2.3.1

2.3.1

Recurly Client Ruby 2.3.2

2.3.2

Recurly Client Ruby 2.3.3

2.3.3

Recurly Client Ruby 2.3.4

2.3.4

Recurly Client Ruby 2.3.5

2.3.5

Recurly Client Ruby 2.3.6

2.3.6

Recurly Client Ruby 2.3.7

2.3.7

Recurly Client Ruby 2.3.8

2.3.8

Recurly Client Ruby 2.3.9

2.3.9

Recurly Client Ruby 2.4.0

2.4.0

Recurly Client Ruby 2.4.1

2.4.1

Recurly Client Ruby 2.4.2

2.4.2

Recurly Client Ruby 2.4.3

2.4.3

Recurly Client Ruby 2.4.4

2.4.4

Recurly Client Ruby 2.4.5

2.4.5

Recurly Client Ruby 2.4.6

2.4.6

Recurly Client Ruby 2.4.7

2.4.7

Recurly Client Ruby 2.4.8

2.4.8

Recurly Client Ruby 2.4.9

2.4.9

Recurly Client Ruby 2.4.10

2.4.10

Recurly Client Ruby 2.5.0

2.5.0

Recurly Client Ruby 2.5.1

2.5.1

Recurly Client Ruby 2.5.2

2.5.2

Recurly Client Ruby 2.5.3

2.5.3

Recurly Client Ruby 2.6.0

2.6.0

Recurly Client Ruby 2.6.1

2.6.1

Recurly Client Ruby 2.6.2

2.6.2

Recurly Client Ruby 2.7.0

2.7.0

Recurly Client Ruby 2.7.1

2.7.1

Recurly Client Ruby 2.7.2

2.7.2

Recurly Client Ruby 2.7.3

2.7.3

Recurly Client Ruby 2.7.4

2.7.4

Recurly Client Ruby 2.7.5

2.7.5

Recurly Client Ruby 2.7.6

2.7.6

Recurly Client Ruby 2.7.7

2.7.7

Recurly Client Ruby 2.8.0

2.8.0

Recurly Client Ruby 2.8.0 Release Candidate 1

2.8.0

Recurly Client Ruby 2.8.0 Release Candidate 3

2.8.0

Recurly Client Ruby 2.8.1

2.8.1

Recurly Client Ruby 2.9.0

2.9.0

Recurly Client Ruby 2.9.1

2.9.1

Recurly Client Ruby 2.10.0

2.10.0

Recurly Client Ruby 2.10.1

2.10.1

Recurly Client Ruby 2.10.2

2.10.2

Recurly Client Ruby 2.10.3

2.10.3

Recurly Client Ruby 2.11.0

2.11.0

Recurly Client Ruby 2.11.1

2.11.1

Recurly Client Ruby 2.11.2

2.11.2

Stay updated

ExploitPedia is constantly evolving. Sign up to receive a notification when we release additional functionality.

Get in touch

If you'd like to report a bug or have any suggestions for improvements then please do get in touch with us using this form. We will get back to you as soon as we can.