[ 
https://issues.apache.org/jira/browse/DERBY-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636981#comment-17636981
 ] 

Bryan Pendleton commented on DERBY-7147:
----------------------------------------

Here's a tiny little bit of instructions on how to run LDAPAuthenticationTest: 
https://issues.apache.org/jira/browse/DERBY-3659?focusedCommentId=12600313&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12600313

There it says:
{code:java}
When the properties are set, and the extra user (kathy/kathyS) is specified, 
the test will run. {code}
It seems like I need to:
 # Figure out how to set the 5 magic properties that need to be set when 
running the test
 # Figure out what data I have to load into my LDAP serverĀ 

The comment in the test source code says:
{code:java}
// This test assumes at least one valid user (to be passed in) and one
// additional user (kathy / kathyS) to be setup in ou=People on the
// LDAPServer.
 {code}

> 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)

Reply via email to