What is CVE-2017-0907?

CVE-2017-0907 is a critical-severity server-side request forgery (SSRF) vulnerability in recurly-api-client (nuget), affecting versions < 1.0.1. It is fixed in 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. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

Which versions of recurly-api-client are affected by CVE-2017-0907?

recurly-api-client (nuget) versions < 1.0.1 is affected.

Is there a fix for CVE-2017-0907?

Yes. CVE-2017-0907 is fixed in 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. Upgrade to this version or later.

Is CVE-2017-0907 exploitable, and should I be worried?

Whether CVE-2017-0907 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-0907 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-0907 in recurly-api-client

Q: Which versions of recurly-api-client are affected by CVE-2017-0907?

recurly-api-client (nuget) versions < 1.0.1 is affected.

Q: Is there a fix for CVE-2017-0907?

Yes. CVE-2017-0907 is fixed in 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. Upgrade to this version or later.

Q: Is CVE-2017-0907 exploitable, and should I be worried?

Whether CVE-2017-0907 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-0907 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-0907?

Upgrade: recurly-api-client to 1.0.1 or later, recurly-api-client to 1.1.10 or later, recurly-api-client to 1.2.8 or later, recurly-api-client to 1.3.2 or later, recurly-api-client to 1.4.14 or later, recurly-api-client to 1.5.3 or later, recurly-api-client to 1.6.2 or later, recurly-api-client to 1.7.1 or later, recurly-api-client to 1.8.1 or later.

Summary

Critical severity vulnerability that affects recurly-api-client

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.

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Affected versions

recurly-api-client (< 1.0.1) recurly-api-client (>= 1.1.0, < 1.1.10) recurly-api-client (>= 1.2.0, < 1.2.8) recurly-api-client (>= 1.3.0, < 1.3.2) recurly-api-client (>= 1.4.0, < 1.4.14) recurly-api-client (>= 1.5.0, < 1.5.3) recurly-api-client (>= 1.6.0, < 1.6.2) recurly-api-client (= 1.7.0) recurly-api-client (= 1.8.0)

Security releases

recurly-api-client → 1.0.1 (nuget) recurly-api-client → 1.1.10 (nuget) recurly-api-client → 1.2.8 (nuget) recurly-api-client → 1.3.2 (nuget) recurly-api-client → 1.4.14 (nuget) recurly-api-client → 1.5.3 (nuget) recurly-api-client → 1.6.2 (nuget) recurly-api-client → 1.7.1 (nuget) recurly-api-client → 1.8.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

recurly-api-client to 1.0.1 or later; recurly-api-client to 1.1.10 or later; recurly-api-client to 1.2.8 or later; recurly-api-client to 1.3.2 or later; recurly-api-client to 1.4.14 or later; recurly-api-client to 1.5.3 or later; recurly-api-client to 1.6.2 or later; recurly-api-client to 1.7.1 or later; recurly-api-client to 1.8.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-0907? CVE-2017-0907 is a critical-severity server-side request forgery (SSRF) vulnerability in recurly-api-client (nuget), affecting versions < 1.0.1. It is fixed in 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. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
Which versions of recurly-api-client are affected by CVE-2017-0907? recurly-api-client (nuget) versions < 1.0.1 is affected.
Is there a fix for CVE-2017-0907? Yes. CVE-2017-0907 is fixed in 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. Upgrade to this version or later.
Is CVE-2017-0907 exploitable, and should I be worried? Whether CVE-2017-0907 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-0907 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-0907?
- Upgrade recurly-api-client to 1.0.1 or later
- Upgrade recurly-api-client to 1.1.10 or later
- Upgrade recurly-api-client to 1.2.8 or later
- Upgrade recurly-api-client to 1.3.2 or later
- Upgrade recurly-api-client to 1.4.14 or later
- Upgrade recurly-api-client to 1.5.3 or later
- Upgrade recurly-api-client to 1.6.2 or later
- Upgrade recurly-api-client to 1.7.1 or later
- Upgrade recurly-api-client to 1.8.1 or later