HTTP Strict Transport Security (HSTS) Missing

1. Executive Threat Overview

HTTP Strict Transport Security (HSTS) is a web security policy mechanism that helps to protect websites against cookie hijacking and protocol downgrade attacks (like SSL stripping). It forces user agents (like browsers) to only interact with the website using secure HTTPS connections, never over plaintext HTTP.

In modern web infrastructure, http strict transport security (hsts) missing represents a critical failure mode in security controls. According to A05:2021 - Security Misconfiguration and documented under CWE-319: Cleartext Transmission of Sensitive Information, 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-319: Cleartext Transmission of Sensitive Information, 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 HTTP Strict Transport Security (HSTS) Missing:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;

Apache 2.4 / .htaccess

# Apache 2.4 Configuration for HTTP Strict Transport Security (HSTS) Missing:
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"

Application Code Implementation

To enable HSTS, add the Strict-Transport-Security header to all secure HTTPS responses. The max-age directive specifies how long the browser should remember this policy (e.g. 1 year):

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

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 | grep -i 'hsts'

6. Frequently Asked Questions