131 – Insecure or unset HTTP headers - Strict Transport Security
Description
The server is missing the Strict-Transport-Security HTTP header. Alternatively, the headers max-age is too short.
Impact
Compromise confidential information sent through insecure channels.
Recommendation
Set the Strict-Transport-Security header with a max-age 63072000 and the includeSubDomains directive on all server responses.
Threat
Unauthorized attacker from adjacent network performing a sniffing attack.
Expected Remediation Time
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: A
- Attack complexity: L
- Attack Requirements: N
- Privileges required: N
- User interaction: A
- Confidentiality (VC): L
- Integrity (VI): N
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
- Exploit maturity: P