Skip to content

Possible ORM Leak Vulnerability in the Harbor

Moderate severity GitHub Reviewed Published Jul 23, 2025 in goharbor/harbor • Updated Jul 25, 2025

Package

gomod github.com/goharbor/harbor (Go)

Affected versions

= 2.13.0
>= 2.4.0-rc1.1, < 2.12.4
< 2.4.0-rc1.0.20250331071157-dce7d9f5cffb

Patched versions

2.13.1
2.12.4
2.4.0-rc1.0.20250331071157-dce7d9f5cffb

Description

Impact

Administrator users on Harbor could exploit an ORM Leak (https://www.elttam.com/blog/plormbing-your-django-orm/) vulnerability that was present in the /api/v2.0/users endpoint to leak users' password hash and salt values. This vulnerability was introduced into the application because the q URL parameter allowed the administrator to filter users by any column, and the filter password=~ could be abused to leak out a user's password hash character by character.

An attacker with administrator access could exploit this vulnerability to leak highly sensitive information stored on the Harbor database, as demonstrated in the attached writeup by the leaking of users' password hashes and salts. All endpoints that support the q URL parameter are vulnerable to this ORM leak attack, and could potentially be exploitable by lower privileged users to gain unauthorised access to other sensitive information.

Patches

No available

Workarounds

NA

References

Credit

[email protected]

References

@stonezdj stonezdj published to goharbor/harbor Jul 23, 2025
Published to the GitHub Advisory Database Jul 23, 2025
Reviewed Jul 23, 2025
Published by the National Vulnerability Database Jul 25, 2025
Last updated Jul 25, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(10th percentile)

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

Exposure of Sensitive Information Through Data Queries

When trying to keep information confidential, an attacker can often infer some of the information by using statistics. Learn more on MITRE.

CVE ID

CVE-2025-30086

GHSA ID

GHSA-h27m-3qw8-3pw8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.