Skip to content
Fencer Intel
medium —

GHSA-prh4-vhfh-24mj json

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

published 7mo ago modified 7mo ago also GO-2026-4876

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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.

Patch / fix

  • go github.com/goharbor/harbor 2.13.5, 2.13.5+incompatible, 2.14.3, 2.14.3+incompatible

Is GHSA-prh4-vhfh-24mj in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/goharbor/harbor
>=2.13.0, <2.13.5
>=2.14.0, <2.14.3
>=2.13.0+incompatible, <2.13.5+incompatible
>=2.14.0+incompatible, <2.14.3+incompatible
2.13.5
2.14.3
2.13.5+incompatible
2.14.3+incompatible

Classification

Weakness
  • CWE-312 Cleartext Storage of Sensitive Information
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.