LDAP server exposes too much information to an unauthenticated query #62

Closed
opened 2021-10-30 15:08:04 +00:00 by a · 2 comments
Owner

Without any authentication, you can query for the usernames and some other sensitive information. Since we are also using SSH on the standard port, an attacker could brute-force a particular user that they found by doing an LDAP query.

Without any authentication, you can query for the usernames and some other sensitive information. Since we are also using SSH on the standard port, an attacker could brute-force a particular user that they found by doing an LDAP query.
a added this to the v5.0 milestone 2021-10-30 15:08:04 +00:00
a added the
security
bug
labels 2021-10-30 15:08:04 +00:00
a self-assigned this 2021-10-30 15:08:04 +00:00
a added this to the (deleted) project 2021-10-30 15:08:04 +00:00
Author
Owner

Eh, this isn't too important since a determined attacker could get the usernames using other methods. The only other "sensitive" info you can get from an unauthenticated LDAP query is their UID number and home directory, which isn't sensitive at all.

Eh, this isn't too important since a determined attacker could get the usernames using other methods. The only other "sensitive" info you can get from an unauthenticated LDAP query is their UID number and home directory, which isn't sensitive at all.
a closed this issue 2021-10-30 15:15:00 +00:00
Author
Owner

While our LDAP server is exposed to the internet, I don't want to mess with LDAP configs since it works and it's probably going to break if I try to tweak things.

While our LDAP server is exposed to the internet, I don't want to mess with LDAP configs since it works and it's probably going to break if I try to tweak things.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: exozyme/exozyme#62
No description provided.