CNCF Harbor 2.13.x before 2.13.1 and 2.12.x before 2.12.4 allows information disclosure by administrators who can exploit an ORM Leak presen
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.12.4+incompatible, 2.13.1+incompatible, 2.13.1, 2.12.4, 2.4.0-rc1.0.20250331071157-dce7d9f5cffb
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
CNCF Harbor 2.13.x before 2.13.1 and 2.12.x before 2.12.4 allows information disclosure by administrators who can exploit an ORM Leak present in the /api/v2.0/users endpoint to leak users' password hash and salt values. The q URL parameter allows a user to filter users by any column, and filter password=~ could be abused to leak out a user's password hash character by character. An attacker with administrator access could exploit this to leak highly sensitive information stored in the Harbor database. All endpoints that support the q URL parameter are vulnerable to this ORM leak attack.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- github.com/goharbor/harborGo
fixed in 2.12.4+incompatible; From 2.13.0+incompatible · fixed in 2.13.1+incompatible
- github.com/goharbor/harborGo
From 2.13.0 · fixed in 2.13.1
- github.com/goharbor/harborGo
From 2.4.0-rc1.1 · fixed in 2.12.4
- github.com/goharbor/harborGo
fixed in 2.4.0-rc1.0.20250331071157-dce7d9f5cffb