Skip to content
Fencer Intel
critical 9.8

CVE-2017-0906 json

Recurly vulnerable to SSRF

published 8y ago modified 4mo ago also GHSA-38rv-5jqc-m2cv , PYSEC-2017-68 , EUVD-2017-0111

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.6%
EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

The Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a Server-Side Request Forgery vulnerability in the "Resource.get" method that could result in compromise of API keys or other critical resources.

Patch / fix

  • pypi recurly 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2

Is CVE-2017-0906 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.62% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi recurly
>=2.6.0, <2.6.2
>=2.5.0, <2.5.1
>=2.4.0, <2.4.5
>=2.3.0, <2.3.1
>=2.2.0, <2.2.22
>=2.1.0, <2.1.16
<2.0.5
>=2.0, <2.0.5
>=2.1, <2.1.16
>=2.2, <2.2.22
>=2.3, <2.3.1
>=2.4, <2.4.5
>=2.5, <2.5.1
>=2.6, <2.6.2
2.6.2
2.5.1
2.4.5
2.3.1
2.2.22
2.1.16
2.0.5

Affected products

  • Recurly recurly python module

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.