-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add sanitizer to ldap account and password #3372
Conversation
fixed: dexidp#3354 Signed-off-by: hsinhoyeh <[email protected]>
Signed-off-by: hsinhoyeh <[email protected]>
3a7b1a8
to
ccab708
Compare
hi @nabokihms knowing you were busy, but this requires your attention. |
Looks good from my point of view. The only thing left is to satisfy the linter. |
Signed-off-by: hsinhoyeh <[email protected]>
b13fb33
to
8fb472d
Compare
fixed, thanks @nabokihms |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's go with this change without additional flags. It sounds like a sane security improvement./ Hope nobody uses wildcards in passwords.
We can add a feature flag if there are such cases.
@hsinhoyeh thank you for your contribution. |
With the change introduced in dexidp#3372 Dex declines passwords that contain special characters. Since password is not passed to any kind of filters, it is safe to pass a password as is. No LDAP query injections are possible. This commit is a revert of password escaping. Signed-off-by: m.nabokikh <[email protected]>
With the change introduced in #3372 Dex declines passwords that contain special characters. Since password is not passed to any kind of filters, it is safe to pass a password as is. No LDAP query injections are possible. This commit is a revert of password escaping. Signed-off-by: m.nabokikh <[email protected]>
With the change introduced in dexidp#3372 Dex declines passwords that contain special characters. Since password is not passed to any kind of filters, it is safe to pass a password as is. No LDAP query injections are possible. This commit is a revert of password escaping. Signed-off-by: m.nabokikh <[email protected]>
Overview
this patch draws error when queys (i.e. account / password) against ldap contain wildcard.
What this PR does / why we need it
fixes #3354
Special notes for your reviewer
not sure whether it would impact the existing usecases or not, but I an open to accept additional switcher to on/off.