You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2026/09/29 03:57:00 UTC
[jira] [Closed] (DIRAPI-473) authenticated flag set before client-side SASL verification completes
[ https://issues.apache.org/jira/browse/DIRAPI-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lécharny closed DIRAPI-473.
------------------------------------
> authenticated flag set before client-side SASL verification completes
> ---------------------------------------------------------------------
>
> Key: DIRAPI-473
> URL: https://issues.apache.org/jira/browse/DIRAPI-473
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.1.8
> Reporter: Emmanuel Lécharny
> Priority: Minor
> Fix For: 2.1.9
>
>
> An application performs a *GSSAPI* bind with mutual _auth_ against a spoofed/*MITM*'d server on a plaintext channel; the attacker returns *SUCCESS* with a bogus final token.
> _evaluateChallenge_ throws, the app logs the failure, but the shared connection still reports _isAuthenticated()==true_ — a pool validator keeps it alive and a later code path reuses the connection to the attacker's endpoint as if mutual _auth_ had succeeded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org