Harbor up to 1.3.0-rc4 ui/api/target.go Ping endpoint server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Harbor up to 1.3.0-rc4. Affected by this issue is the function Ping of the file ui/api/target.go. Performing a manipulation of the argument endpoint as part of Parameter results in server-side request forgery.
This vulnerability is reported as CVE-2017-17697. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in Harbor up to 1.3.0-rc4. This affects the function Ping of the file ui/api/target.go. The manipulation of the argument endpoint as part of a Parameter 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. The summary by CVE is:
The Ping() function in ui/api/target.go in Harbor through 1.3.0-rc4 has SSRF via the endpoint parameter to /api/targets/ping.
The bug was discovered 12/07/2017. The weakness was disclosed 12/15/2017 (Website). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2017-17697 since 12/15/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 8 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.3
VulDB Temp Score: 8.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.6
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/07/2017 🔍12/15/2017 🔍
12/15/2017 🔍
12/15/2017 🔍
12/16/2017 🔍
01/18/2023 🔍
Sources
Advisory: 3755Status: Not defined
CVE: CVE-2017-17697 (🔍)
GCVE (CVE): GCVE-0-2017-17697
GCVE (VulDB): GCVE-100-110727
Entry
Created: 12/16/2017 16:28Updated: 01/18/2023 09:40
Changes: 12/16/2017 16:28 (58), 12/15/2019 15:26 (1), 01/18/2023 09:40 (3)
Complete: 🔍
Cache ID: 216:FF6:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.