RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 782442 - mod_authz_ldap logs the plain text password from AuthzLDAPBindPassword in Apache's log files when it is invalid.
Summary: mod_authz_ldap logs the plain text password from AuthzLDAPBindPassword in Apa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mod_authz_ldap
Version: 6.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Joe Orton
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 14:04 UTC by Aleksander Adamowski
Modified: 2012-10-18 11:44 UTC (History)
2 users (show)

Fixed In Version: mod_authz_ldap-0.26-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-18 11:44:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1389 0 normal SHIPPED_LIVE mod_authz_ldap bug fix update 2012-10-18 15:42:31 UTC

Description Aleksander Adamowski 2012-01-17 14:04:30 UTC 
Description of problem:

mod_authz_ldap logs the plain text password from AuthzLDAPBindPassword in Apache's log files when it is invalid.

Version-Release number of selected component (if applicable):

# rpm -q mod_authz_ldap-0.26-15.el6.x86_64
mod_authz_ldap-0.26-15.el6.x86_64



How reproducible:
always


Steps to Reproduce:
1. Configure LDAP authentication using mod_authz_ldap:

LoadModule authz_ldap_module modules/mod_authz_ldap.so
<IfModule mod_authz_ldap.c>
<Location />
        AuthType Basic
        AuthName "Supply login/password for LDAP authentication"
        AuthzLDAPMethod "ldap"
        AuthzLDAPServer "ldap.example.com"
        AuthzLDAPUserBase "dc=example,dc=com"
        AuthzLDAPUserKey "uid"
        AuthzLDAPUserScope "base"
        AuthzLDAPBindDN "uid=someaccount,dc=example,dc=com"
        AuthzLDAPBindPassword "somepassword"
        require valid-user
</Location>
</IfModule>

2. Set the password for uid=someaccount,dc=example,dc=com to be something different than "somepassword"

3. Try authenticating using HTTP Basic Auth, giving any login/password
  
Actual results:

cannot bind to [2503] LDAP Server as uid=someaccount,dc=example,dc=com/somepassword: 49

Expected results:

Plain text passwords should never be logged in Apache's log files.

Logs are often shipped to other, less secure hosts, archived etc.

Logging passwords significantly increases risks of their leak to unauthorized parties.

For diagnostic purposes, it would be acceptable if logging plain passwords would be configurable using a dedicated configuration option, which would be documented with adequate warnings against its indiscriminate use.
Comment 2 Jan Lieskovsky 2012-01-20 13:43:01 UTC 
Red Hat Security Response Team would not consider this issue to be a security flaw. Though it is definitely a bug, the Apache httpd web server's log files are not accessible by unprivileged user. A privileged user can view the particular password directly. When the particular password would leak due improper Apache httpd web server log files archive / backup process, then it is question of deficiency in the way archives are created.
Comment 4 Suzanne Logcher 2012-02-14 23:28:19 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 5 Joe Orton 2012-05-23 14:02:04 UTC 
Thanks for the report.  I don't see a good reason for the password to be in there, so we could remove it.
Comment 7 RHEL Program Management 2012-07-10 08:31:38 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 8 RHEL Program Management 2012-07-11 00:01:16 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 14 errata-xmlrpc 2012-10-18 11:44:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1389.html
Note You need to log in before you can comment on or make changes to this bug.