cve.bz

CVE-2017-0907 recurly recurly client .net: SSRF

9.8 criticalEPSS 2.6%Fix available

Critical (9.8) in recurly recurly client .net. EPSS 2.6% estimated probability of exploitation activity in the next 30 days. Fixed in recurly-api-client 1.0.1, 1.1.10, 1.2.8.

On this page
The Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vulnerable to a Server-Side Request Forgery vulnerability due to incorrect use of "Uri.EscapeUriString" that could result in compromise of API keys or other critical resources.

Severity

CVSS 3.0

9.8 critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
2.6% (unchanged from 2.6% a week ago; 2.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-0907 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-0907?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-0907?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-0907 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
recurly:recurly_client_.net1.0.0
recurly:recurly_client_.net1.0.0:beta1
recurly:recurly_client_.net1.0.0:beta2
recurly:recurly_client_.net1.0.0:beta3
recurly:recurly_client_.net1.0.0:rc1
recurly:recurly_client_.net1.0.0.1
recurly:recurly_client_.net1.0.0.2
recurly:recurly_client_.net1.0.0.3
recurly:recurly_client_.net1.0.0.4
recurly:recurly_client_.net1.1.0
recurly:recurly_client_.net1.1.1
recurly:recurly_client_.net1.1.4
recurly:recurly_client_.net1.1.5
recurly:recurly_client_.net1.1.6
recurly:recurly_client_.net1.1.7
recurly:recurly_client_.net1.1.8
recurly:recurly_client_.net1.1.9
recurly:recurly_client_.net1.2.0
recurly:recurly_client_.net1.2.1
recurly:recurly_client_.net1.2.2
recurly:recurly_client_.net1.2.5
recurly:recurly_client_.net1.2.6
recurly:recurly_client_.net1.2.7
recurly:recurly_client_.net1.3.0
recurly:recurly_client_.net1.3.1
recurly:recurly_client_.net1.4.0
recurly:recurly_client_.net1.4.1
recurly:recurly_client_.net1.4.2
recurly:recurly_client_.net1.4.3
recurly:recurly_client_.net1.4.4
recurly:recurly_client_.net1.4.5
recurly:recurly_client_.net1.4.6
recurly:recurly_client_.net1.4.7
recurly:recurly_client_.net1.4.8
recurly:recurly_client_.net1.4.9
recurly:recurly_client_.net1.4.10
recurly:recurly_client_.net1.4.11
recurly:recurly_client_.net1.4.12
recurly:recurly_client_.net1.4.13
recurly:recurly_client_.net1.5.0
recurly:recurly_client_.net1.6.0
recurly:recurly_client_.net1.6.1
recurly:recurly_client_.net1.7.0
recurly:recurly_client_.net1.8.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client<1.0.11.0.1
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.1.0 <1.1.101.1.10
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.2.0 <1.2.81.2.8
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.3.0 <1.3.21.3.2
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.4.0 <1.4.141.4.14
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.5.0 <1.5.31.5.3
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.6.0 <1.6.21.6.2
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.7.0 <1.7.11.7.1
GHSA-xpwp-rq3x-x6v7NuGetrecurly-api-client>=1.8.0 <1.8.11.8.1

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON