cve.bz

CVE-2017-17697 linuxfoundation harbor: SSRF

8.6 highExploit referenceEPSS 1.4%

High (8.6) in linuxfoundation harbor. EPSS 1.4% estimated probability of exploitation activity in the next 30 days.

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.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 73rd 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

Ask an AI about this CVE

Show the promptExplain CVE-2017-17697 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-17697?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-17697?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-17697 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
linuxfoundation:harborbefore 1.3.0
linuxfoundation:harbor1.3.0
linuxfoundation:harbor1.3.0:rc1
linuxfoundation:harbor1.3.0:rc2
linuxfoundation:harbor1.3.0:rc3
linuxfoundation:harbor1.3.0:rc4

Attack patterns (CAPEC)

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

References

Check your stackJSON