SSH PermitRootLogin over Password

1. Executive Threat Overview

Allowing direct root login over SSH using passwords makes servers highly susceptible to brute-force attacks. Root actions should be audited and require private keys.

In modern web infrastructure, ssh permitrootlogin over password represents a critical failure mode in security controls. According to A07:2021 - Identification and Authentication Failures and documented under CWE-306: Missing Authentication for Critical Function, applications failing to enforce proper controls at this layer expose their attack surface to automated crawlers, botnets, and skilled penetration testers.

When evaluating target perimeters, threat actors systematically probe for this condition using fingerprinting engines like Nmap, Nuclei, and custom fuzzing scripts. If left unresolved, this weakness can be chained with auxiliary application vulnerabilities to achieve elevated privileges, exfiltrate sensitive data, or bypass downstream security filters.

2. Technical & Business Impact

3. Exploitation Mechanics & Attack Vectors

Threat actors identify and exploit this weakness through the following attack phases:

1. Phase 1 (Reconnaissance): The attacker performs automated reconnaissance against the target domain to identify server headers, software versions, and security configurations.
2. Phase 2 (Exploitation): Utilizing known attack vectors associated with CWE-306: Missing Authentication for Critical Function, the attacker crafts specific payloads or request patterns to trigger the vulnerability.
3. Phase 3 (Post-Exploitation & Impact): Upon successful validation, the attacker leverages the condition to compromise confidential records, manipulate user sessions, or pivot toward internal services.

4. Production Hardening & Remediation

To eliminate this vulnerability, apply the following hardened configurations to your edge web server or application codebase:

Nginx Web Server Configuration

# Recommended Nginx Hardening Configuration for SSH PermitRootLogin over Password:
# Apply strict security directives in the relevant server or location block
# Refer to CWE-306: Missing Authentication for Critical Function remediation standards.

Apache 2.4 / .htaccess

# Apache 2.4 Configuration for SSH PermitRootLogin over Password:
# Configure Apache directives in httpd.conf or .htaccess
# Refer to A07:2021 - Identification and Authentication Failures guidelines.

Application Code Implementation

Set PermitRootLogin no or PermitRootLogin prohibit-password in /etc/ssh/sshd_config. Enforce SSH key-based authentication and disable password login entirely.

5. Verification & Testing Commands

Run the following terminal command to audit and verify that your production fixes are actively enforced:

curl -sI https://example.com/ssh

6. Frequently Asked Questions