Skip to content

Conversation

@ulyssefontainecagip
Copy link

No description provided.

@ulyssefontainecagip ulyssefontainecagip force-pushed the fix/filter_username_input branch from d1f19b0 to c8e3f85 Compare March 29, 2023 12:30
Copy link
Contributor

@evrardjp evrardjp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't test this myself, but the tests do make sense.

Copy link
Contributor

@evrardjp evrardjp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edit: Can you squash the CI changes into a different PR, and keep this PR clean to contain only the change, please?

@ulyssefontainecagip ulyssefontainecagip force-pushed the fix/filter_username_input branch from c8e3f85 to 867c9dc Compare April 28, 2023 14:01
@ulyssefontainecagip
Copy link
Author

CI changes was moved to PR #25 👍

@evrardjp
Copy link
Contributor

@zkonak can you check why this is pending?

Without this, it is possible to do an ldap query injection.
This is a problem as it is a possible vulnerability issue.
However, it is very unlikely to arrive to real case exploitation,
as the input is admin given.

This fixes it by ensuring filtering with a regexp and adding the
appropriate tests (here done with fuzzing).

Co-Authored-By: Jean-Philippe Evrard <jean-philippe.evrard-prestataire@ca-gip.fr>
@evrardjp-cagip evrardjp-cagip force-pushed the fix/filter_username_input branch from 867c9dc to 71826e8 Compare December 17, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants