[
https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637439#comment-17637439
]
Bryan Pendleton commented on DERBY-7147:
----------------------------------------
My attempts to connect to the ApacheDS server using the built-in Apache
Directory Studio tool are successful, so the LDAP server itself seems to be
working; I just don't understand how to configure the derby.properties for LDAP
Authentication to match what the ApacheDS server wants, and the error message I
get back from it isn't giving any hints about what's wrong (this is a common
problem with security-related tools, their error messages are often opaque,
because giving too much information is often felt to be a security risk in
itself).
Sigh.
> LDAP injection vulnerability in LDAPAuthenticationImpl
> ------------------------------------------------------
>
> Key: DERBY-7147
> URL: https://issues.apache.org/jira/browse/DERBY-7147
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.16.1.1
> Reporter: Richard N. Hillegas
> Assignee: Richard N. Hillegas
> Priority: Major
> Attachments: derby-7147-01-aa-reformatForReadability.diff,
> derby-7147-02-aa-escapeLDAPsearchFilter.diff
>
>
> An LDAP injection vulnerability has been identified in
> LDAPAuthenticationSchemeImpl.getDNFromUID(). An exploit has not been
> provided, but there is a possibility that an intruder could bypass
> authentication checks in Derby-powered applications which rely on external
> LDAP servers.
> For more information on LDAP injection, see
> https://www.synopsys.com/glossary/what-is-ldap-injection.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
