feat: add debian12 scripts

- sudo_re_authenticate.sh -> 5.2.5 - pam_pwhistory_enabled.sh -> 5.3.2.4 - pam_faillock_enabled.sh -> 5.3.2.2 This is an updated version of enable_lockout_failed_password.sh (renamed) - pam_unix_enabled.sh -> 5.3.2.1 - password_failed_lockout.sh -> 5.3.3.1.1 - password_unlock_time.sh -> 5.3.3.1.2 - password_root_unlock.sh -> 5.3.3.1.3
2025-09-04 21:48:23 +02:00 · 2025-08-08 16:12:00 +02:00
parent 1926758707
commit 37b4f5982e
17 changed files with 814 additions and 116 deletions
--- a/bin/hardening/pam_faillock_enabled.sh
+++ b/bin/hardening/pam_faillock_enabled.sh
@@ -0,0 +1,90 @@
+#!/bin/bash
+
+# run-shellcheck
+#
+# CIS Debian Hardening
+#
+
+#
+# Ensure pam_faillock module is enabled (Automated)
+#
+
+set -e # One error, it's over
+set -u # One variable unset, it's over
+
+# shellcheck disable=2034
+HARDENING_LEVEL=3
+# shellcheck disable=2034
+DESCRIPTION="Ensure pam_faillock module is enabled"
+
+PAM_FILES="/etc/pam.d/common-auth /etc/pam.d/common-account"
+PAM_PATTERN="^[^#].*pam_faillock.so"
+
+# This function will be called if the script status is on enabled / audit mode
+audit() {
+    PAM_VALID=0
+
+    for PAM_FILE in $PAM_FILES; do
+        if grep "$PAM_PATTERN" "$PAM_FILE" >/dev/null 2>&1; then
+            info "pam_faillock found in $PAM_FILE"
+        else
+            crit "pam_faillock not found in $PAM_FILE"
+            PAM_VALID=1
+        fi
+    done
+
+    if [ "$PAM_VALID" -eq 0 ]; then
+        ok "pam_faillock is enabled"
+    fi
+}
+
+# This function will be called if the script status is on enabled mode
+apply() {
+    if [ "$PAM_VALID" -ne 0 ]; then
+        # check if already present in an pam-auth-update profile
+        # if not
+        # - add in a profile
+        # then in all cases : pam-auth-update --enable {PROFILE_NAME}
+        if ! grep "$PAM_PATTERN" /usr/share/pam-configs/*; then
+            pam_update_profile="faillock faillock_notify"
+            arr=('Name: Enable pam_faillock to deny access' 'Default: yes' 'Priority: 0' 'Auth-Type: Primary' 'Auth:' '   [default=die] pam_faillock.so authfail')
+            printf '%s\n' "${arr[@]}" >/usr/share/pam-configs/failock
+
+            arr=('Name: Notify of failed login attempts and reset count upon success' 'Default: yes' 'Priority: 1024' 'Auth-Type: Primary' 'Auth:' '    requisite         pam_faillock.so preauth' 'Account-Type: Primary' 'Account:' '   required pam_faillock.so')
+            printf '%s\n' "${arr[@]}" >/usr/share/pam-configs/faillock_notify
+
+        else
+            pam_update_profile="$(grep -l "$PAM_PATTERN" /usr/share/pam-configs/* | paste -s)"
+        fi
+
+        info "Applying 'pam-auth-update' to enable pam_faillock.so"
+        for profile in $pam_update_profile; do
+            DEBIAN_FRONTEND='noninteractive' pam-auth-update --force --enable "$profile"
+        done
+    fi
+}
+
+# This function will check config parameters required
+check_config() {
+    :
+}
+
+# Source Root Dir Parameter
+if [ -r /etc/default/cis-hardening ]; then
+    # shellcheck source=../../debian/default
+    . /etc/default/cis-hardening
+fi
+if [ -z "$CIS_LIB_DIR" ]; then
+    echo "There is no /etc/default/cis-hardening file nor cis-hardening directory in current environment."
+    echo "Cannot source CIS_LIB_DIR variable, aborting."
+    exit 128
+fi
+
+# Main function, will call the proper functions given the configuration (audit, enabled, disabled)
+if [ -r "${CIS_LIB_DIR}"/main.sh ]; then
+    # shellcheck source=../../lib/main.sh
+    . "${CIS_LIB_DIR}"/main.sh
+else
+    echo "Cannot find main.sh, have you correctly defined your root directory? Current value is $CIS_LIB_DIR in /etc/default/cis-hardening"
+    exit 128
+fi