Skip to content

GHSA-prh4-vhfh-24mj GO-2026-4876

Harbor: LDAP password and OIDC secret are not redacted in the audit log

Medium Go
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-312 Cleartext Storage of Sensitive Information
CWE-532 Insertion of Sensitive Information into Log File
Fix
2.13.5
Upgrade github.com/goharbor/harbor to this version or later

Description

Impact

Harbor write configuration payload to audit log when configuration change, the ldap_search_password and oidc_client_secret will be logged in the audit log without redacted

Patches

Harbor v2.15.0, v2.14.3, v2.13.5

Workarounds

Disable audit log configure event in Harbor Web Console: Go to Administration -> Configuration -> Enable Audit Log Event Type -> Uncheck "Update Configuration" and click "Save" Button.

Affected versions

Go

PackageVulnerableFixed in
github.com/goharbor/harbor
>= 2.13.0, < 2.13.5
2.13.5
github.com/goharbor/harbor
>= 2.14.0, < 2.14.3
2.14.3
github.com/goharbor/harbor
>= 2.13.0+incompatible, < 2.13.5+incompatible
>= 2.14.0+incompatible, < 2.14.3+incompatible
2.13.5+incompatible
2.14.3+incompatible

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/goharbor/harbor Go → 2.13.5

go
go get github.com/goharbor/harbor@v2.13.5 && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
High
User interaction
None
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

Weakness

CWE-312: Cleartext Storage of Sensitive Information

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

How to prevent it
  • Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301]
  • Implementation, System Configuration, Operation: In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-hj7x-hmf2-hc2p
Harbor allows the use of the default password for web UI login
Critical Also affects github.com/goharbor/harbor
GHSA-h27m-3qw8-3pw8
Possible ORM Leak Vulnerability in the Harbor
Medium Also affects github.com/goharbor/harbor
GHSA-f9vc-vf3r-pqqq
Harbor repository description page has Cross-site Scripting vulnerability
Medium Also affects github.com/goharbor/harbor
GHSA-r864-28pw-8682
Harbor fails to validate the user permissions when updating p2p preheat policies
High Also affects github.com/goharbor/harbor
GHSA-hw28-333w-qxp3
Harbor fails to validate the user permissions when updating project configurations
Medium Also affects github.com/goharbor/harbor
GHSA-vw63-824v-qf2j
SQL Injection in Harbor scan log API
Medium Also affects github.com/goharbor/harbor
GHSA-5757-v49g-f6r7
Open Redirect URL in Harbor
Medium Also affects github.com/goharbor/harbor
GHSA-mq6f-5xh5-hgcf
Harbor timing attack risk
Medium Also affects github.com/goharbor/harbor
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor