Org.openidentityplatform.opendj:opendj server legacy: OpenDJ SASL PLAIN authzid bypassing the proxy ACI scope check
A vulnerability in OpenDJ server legacy versions prior to 5.1.2 allows an attacker with the proxied-auth privilege to bypass proxy access control checks when using SASL PLAIN authentication with an authorization identity (authzid). This flaw permits privilege escalation by impersonating arbitrary non-root directory users beyond the intended proxy ACI restrictions. The issue arises because the SASL PLAIN authzid path does not enforce the mayProxy scope check, unlike other proxy paths. The vulnerability is critical and can be mitigated by upgrading to version 5.1.2 or later or restricting the proxied-auth privilege until patched.
AI Analysis
Technical Summary
OpenDJ server legacy versions before 5.1.2 contain a vulnerability in the SASL PLAIN bind mechanism where supplying an authorization identity (authzid) that resolves to a different user bypasses the proxy access control instruction (ACI) scope check. Specifically, the PlainSASLMechanismHandler verifies only the PROXIED_AUTH privilege but does not evaluate the 'proxy' access-control right (mayProxy ACI scope). Consequently, any account with the proxied-auth privilege can impersonate any resolvable non-root identity without the required proxy ACI grant. This behavior deviates from other proxy paths like DIGEST-MD5 and GSSAPI, which require both privilege and mayProxy scope. The vulnerability enables privilege escalation and authorization bypass, allowing unauthorized impersonation of directory users. The fix involves enforcing the mayProxy scope check on the SASL PLAIN authzid path and returning INVALID_CREDENTIALS before password verification to prevent information leakage. Until patched, restricting or revoking the proxied-auth privilege is recommended.
Potential Impact
An attacker holding the proxied-auth privilege can escalate privileges by impersonating arbitrary directory users beyond the scope intended by proxy ACIs, effectively bypassing authorization controls. This compromises confidentiality and integrity of directory data for affected users. The root or Directory Manager accounts cannot be assumed via this method. The vulnerability does not impact availability.
Mitigation Recommendations
A fix is available in OpenDJ server legacy version 5.1.2 that enforces the mayProxy scope check on the SASL PLAIN authzid path, aligning it with other proxy authorization mechanisms. Until upgrading, it is recommended to restrict or revoke the proxied-auth privilege to prevent exploitation. No other mitigations are specified.
Org.openidentityplatform.opendj:opendj server legacy: OpenDJ SASL PLAIN authzid bypassing the proxy ACI scope check
Description
A vulnerability in OpenDJ server legacy versions prior to 5.1.2 allows an attacker with the proxied-auth privilege to bypass proxy access control checks when using SASL PLAIN authentication with an authorization identity (authzid). This flaw permits privilege escalation by impersonating arbitrary non-root directory users beyond the intended proxy ACI restrictions. The issue arises because the SASL PLAIN authzid path does not enforce the mayProxy scope check, unlike other proxy paths. The vulnerability is critical and can be mitigated by upgrading to version 5.1.2 or later or restricting the proxied-auth privilege until patched.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenDJ server legacy versions before 5.1.2 contain a vulnerability in the SASL PLAIN bind mechanism where supplying an authorization identity (authzid) that resolves to a different user bypasses the proxy access control instruction (ACI) scope check. Specifically, the PlainSASLMechanismHandler verifies only the PROXIED_AUTH privilege but does not evaluate the 'proxy' access-control right (mayProxy ACI scope). Consequently, any account with the proxied-auth privilege can impersonate any resolvable non-root identity without the required proxy ACI grant. This behavior deviates from other proxy paths like DIGEST-MD5 and GSSAPI, which require both privilege and mayProxy scope. The vulnerability enables privilege escalation and authorization bypass, allowing unauthorized impersonation of directory users. The fix involves enforcing the mayProxy scope check on the SASL PLAIN authzid path and returning INVALID_CREDENTIALS before password verification to prevent information leakage. Until patched, restricting or revoking the proxied-auth privilege is recommended.
Potential Impact
An attacker holding the proxied-auth privilege can escalate privileges by impersonating arbitrary directory users beyond the scope intended by proxy ACIs, effectively bypassing authorization controls. This compromises confidentiality and integrity of directory data for affected users. The root or Directory Manager accounts cannot be assumed via this method. The vulnerability does not impact availability.
Mitigation Recommendations
A fix is available in OpenDJ server legacy version 5.1.2 that enforces the mayProxy scope check on the SASL PLAIN authzid path, aligning it with other proxy authorization mechanisms. Until upgrading, it is recommended to restrict or revoke the proxied-auth privilege to prevent exploitation. No other mitigations are specified.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p279-2cqp-84jg
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["Maven"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a6542219c2644c7f80884e3
Added to database: 07/25/2026, 23:09:21 UTC
Last enriched: 07/25/2026, 23:52:44 UTC
Last updated: 07/26/2026, 03:44:24 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.