Vulnerability in org.openidentityplatform.opendj:opendj-server-legacy (CVE-2026-73644)
Summary
Vulnerability in org.openidentityplatform.opendj:opendj-server-legacy (CVE-2026-73644). Confidential information can be exposed externally. Mitigation: upgrade to 5.1.2 or later.
Original description
The description as published by the source.
Summary
When a SASL PLAIN bind supplies an authorization identity (authzid) that resolves to a different user, PlainSASLMechanismHandler verified only the PROXIED_AUTH privilege and never evaluated the "proxy" access-control right (the mayProxy ACI scope check). As a result, any account holding the proxied-auth privilege could assume any resolvable non-root identity without being granted a proxy ACI for that target.
This diverges from every other proxy path in OpenDJ — the proxied-authorization controls (RFC 4370) and the DIGEST-MD5 / GSSAPI authzid handlers all require both the privilege and the mayProxy scope grant.
Impact
Privilege escalation / authorization bypass: a holder of proxied-auth can act as arbitrary directory users beyond the scope intended by the deployment's proxy ACIs, defeating the ACI-based restriction on which identities may be impersonated. Root/Directory Manager is not assumable this way.
Fix
Enforce the mayProxy scope check on the SASL PLAIN authzid path (both dn: and u:/bare forms), sharing one hasProxyAccess helper with the DIGEST-MD5/GSSAPI path. Denial returns INVALID_CREDENTIALS (49) before password verification — matching DIGEST-MD5/GSSAPI — so an unauthenticated client cannot distinguish a missing privilege from a missing ACI grant.
Workaround
Restrict or revoke the proxied-auth privilege until upgraded.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73644 has been found in org.openidentityplatform.opendj:opendj-server-legacy.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade org.openidentityplatform.opendj:opendj-server-legacy to 5.1.2 or later.
If unsure, ask your IT team or search "org.openidentityplatform.opendj:opendj-server-legacy CVE-2026-73644" on the vendor's site.
CVE-2026-73644 (org.openidentityplatform.opendj:opendj-server-legacy) — CWE-285 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.1.2 — apply immediately
Workaround: Restrict or revoke the proxied-auth privilege until upgraded.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in org.openidentityplatform.opendj:opendj-server-legacy.
Check the vendor advisory for the affected versions of org.openidentityplatform.opendj:opendj-server-legacy.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 5.1.2.
Workaround: Restrict or revoke the proxied-auth privilege until upgraded.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.openidentityplatform.opendj:opendj-server-legacy を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
Restrict or revoke the proxied-auth privilege until upgraded.パッチが適用されるまでの応急処置として、Restrict or revoke the proxied-auth privilege until upgraded. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade org.openidentityplatform.opendj:opendj-server-legacy to 5.1.2ステージング環境で 5.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com