[
https://issues.apache.org/jira/browse/DIRAPI-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lécharny resolved DIRAPI-460.
--------------------------------------
Resolution: Fixed
Fixed with commit 76cb5ee0cca62d4689c87ca0817895202cc0e42d
> ComplexDnParser silently discards trailing garbage after last RDN
> -----------------------------------------------------------------
>
> Key: DIRAPI-460
> URL: https://issues.apache.org/jira/browse/DIRAPI-460
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 2.1.8
> Reporter: Emmanuel Lécharny
> Priority: Major
> Fix For: 2.1.9
>
>
> An application validates a user-supplied *DN* with _Dn.isValid()/new
> Dn(input) _and forwards _dn.getName()_.
> The attacker submits '_uid=jsmith\\2C<,uid=admin,ou=system_' — the complex
> parser validates only '_uid=jsmith,_' yet _getName() _returns the whole
> string.
> A downstream stricter parser (*OpenLDAP*, *JNDI LdapName*) reads it as ending
> with '_uid=admin,ou=system_', enabling identity/authorization confusion
> between validating and consuming components.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
