Skip to content
StrikeOps

Missing HTTP Strict Transport Security (HSTS) Header

LowTypical severity Web applications and APIsCWE-319

01Description

The application did not return a Strict-Transport-Security (HSTS) header on HTTPS responses.

02Impact

Without HSTS, a user's browser may make an initial connection over HTTP, which an attacker on the same network can intercept and keep downgraded (SSL stripping), exposing session cookies and credentials.

03Severity

Typically

Low

Typically Low. Usually Low. Raise to Medium for applications handling authentication or sensitive data where users are likely to use untrusted networks.

04How to verify

  1. 1Request the application over HTTPS and inspect response headers for Strict-Transport-Security.
  2. 2Check whether HTTP requests redirect to HTTPS.
  3. 3Check the domain's status on the HSTS preload list.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Return Strict-Transport-Security: max-age=31536000; includeSubDomains on all HTTPS responses once all subdomains support HTTPS.
  2. 2Redirect all HTTP requests to HTTPS.
  3. 3Consider adding the preload directive and submitting the domain to the HSTS preload list.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo