Back

HIGH

samba: Bad password count in AD DC not always effective

Published Nov 28, 2018

Description

Samba from version 4.9.0 and before version 4.9.3 that have AD DC configurations watching for bad passwords (to restrict brute forcing of passwords) in a window of more than 3 minutes may not watch for bad passwords at all. The primary risk from this issue is with regards to domains that have been upgraded from Samba 4.8 and earlier. In these cases the manual testing done to confirm an organisation's password policies apply as expected may not have been re-done after the upgrade.

Affected products

Remediation

Red Hat statement

This flaw does not affect the version of samba shipped with Red Hat Enterprise Linux because there is no support for samba as Active Directory Domain Controller.

Red Hat mitigation

Bad password lockout is not configured by default, it is only effective if a threshold has been set with (eg): samba-tool domain passwordsettings set --account-lockout-threshold=3 To mitigate the issue set a shorter 'Reset account lockout after' window (the ineffective default is 30, anything less than 15 will work): samba-tool domain passwordsettings set --reset-account-lockout-after=15 NOTE: If a fine-grained password policy (PSO) is set, this must also be done on each PSO.

Metrics

Weaknesses (1)

References (9)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner redhat
Published Nov 28, 2018
Updated Aug 5, 2024
Reserved Sep 11, 2018
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Nov 20, 2018