Recurly Client Python Library up to 2.6.1 API Key Resource.get server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Recurly Client Python Library up to 2.6.1. Affected by this issue is the function Resource.get of the component API Key Handler. The manipulation results in server-side request forgery.
This vulnerability was named CVE-2017-0906. The attack may be performed from remote. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, was found in Recurly Client Python Library up to 2.6.1 (Software Library). Affected is the function Resource.get of the component API Key Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The bug was discovered 11/09/2017. The weakness was presented 11/13/2017 (Website). The advisory is shared for download at dev.recurly.com. This vulnerability is traded as CVE-2017-0906 since 11/30/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1 or 2.6.2 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
- 2.0
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.1
- 2.1.0
- 2.1.1
- 2.1.2
- 2.1.3
- 2.1.4
- 2.1.5
- 2.1.6
- 2.1.7
- 2.1.8
- 2.1.9
- 2.1.10
- 2.1.11
- 2.1.12
- 2.1.13
- 2.1.14
- 2.1.15
- 2.2
- 2.2.0
- 2.2.1
- 2.2.2
- 2.2.3
- 2.2.4
- 2.2.5
- 2.2.6
- 2.2.7
- 2.2.8
- 2.2.9
- 2.2.10
- 2.2.11
- 2.2.12
- 2.2.13
- 2.2.14
- 2.2.15
- 2.2.16
- 2.2.17
- 2.2.18
- 2.2.19
- 2.2.20
- 2.2.21
- 2.3
- 2.3.0
- 2.4
- 2.4.0
- 2.4.1
- 2.4.2
- 2.4.3
- 2.4.4
- 2.5.0
- 2.6.0
- 2.6.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Recurly Client Python Library 2.0.5/2.1.16/2.2.22/2.3.1/2.4.5/2.5.1/2.6.2
Patch: github.com
Timeline
11/30/2016 🔍11/09/2017 🔍
11/13/2017 🔍
11/13/2017 🔍
11/14/2017 🔍
01/10/2023 🔍
Sources
Advisory: 049c74699ce93cf126feff06d632ea63fba36742Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-0906 (🔍)
GCVE (CVE): GCVE-0-2017-0906
GCVE (VulDB): GCVE-100-109308
Entry
Created: 11/14/2017 14:13Updated: 01/10/2023 09:45
Changes: 11/14/2017 14:13 (59), 12/05/2019 17:28 (2), 01/10/2023 09:45 (5)
Complete: 🔍
Cache ID: 216:A79:103
No comments yet. Languages: en.
Please log in to comment.