Bug 48037 - Disable security related attribute values in directory-logger logs
Disable security related attribute values in directory-logger logs
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-10-22 15:37 CEST by Nico Stöckigt
Modified: 2021-05-14 16:34 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Security Issue
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018102221000386
Bug group (optional):
Max CVSS v3 score: 5.3 (CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2018-10-22 15:37:26 CEST
In the directory-logger log '/var/log/univention/directory-logger.log' there are security related attributes (krb5key, sambyNTPassword, sambaPasswordHistory, userPassword and pwhistory). It should be configurable to exclude or obscure these attributes.
Comment 1 Arvid Requate univentionstaff 2018-10-29 19:26:25 CET
The original purpose of the directory logger is auditing LDAP changes in blockchain style. The file should be readable only for root. If the data is not included there, the root user can do a slapcat at any time to learn the current hashes, so IMHO there is no gain in security. But maybe there are valid reasons for filtering beyond my current grasp.
Comment 2 Arvid Requate univentionstaff 2018-10-29 19:28:04 CET
There you go, the Ticket has the explanation:

"we would like to send the logs over the network to our central logging system."
Comment 3 Ingo Steuwer univentionstaff 2021-05-14 15:41:48 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.