136 – Insecure or unset HTTP headers - Cache Control
Description
The application lacks the Cache Control security header or sets the header in a insecure value.
Impact
- Store sever responses with sensitive information in the browsers cache. - Produce potentially harmful server responses using Cache Poison attacks.
Recommendation
Set the Cache Control header in the server responses using a secure value such as no-store , no-cache and must-revalidate.
Threat
Unauthorized attacker from local network.
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: H
- 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