Project

General

Profile

Actions
Copy link

Bug #2326

closed

Erroneous successful webGUI authentication with blank password and AD authentication backend

Added by Kane Rason over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
2.1
Start date:
03/30/2012
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:

Description

Erroneous successful authentication to the webGUI when using Active Directory authentication and no password is specified.

Possible fix by adding blank password check to ldap_backed function:

if(!$passwd) {
log_error("ERROR! No password entered.");
return false;
}

Actions
Copy link
 #1

Updated by Kane Rason over 12 years ago

This behaviour is detailed in section 5.1 of rfc 2829 - http://www.ietf.org/rfc/rfc2829.txt

5.1. Anonymous authentication procedure

An LDAP client which has not successfully completed a bind operation
   on a connection is anonymously authenticated.
An LDAP client MAY also specify anonymous authentication in a bind
   request by using a zero-length OCTET STRING with the simple
   authentication choice.

A blank password equates to an anonymous authentication bind request.

Actions
Copy link
 #2

Updated by Chris Buechler over 12 years ago

  • Category changed from Web Interface to User Manager / Privileges
  • Target version set to 2.1
Actions
Copy link
 #3

Updated by Ermal Luçi over 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Ermal Luçi over 12 years ago

Actions
Copy link
 #5

Updated by Chris Buechler over 11 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF