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

⌚ minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the src.

Base

• Attack vector: A
• Attack complexity: H
• Privileges required: N
• User interaction: R
• Scope: U
• Confidentiality: L
• Integrity: N
• Availability: N

Temporal

• Exploit code madurity: P
• Remediation level: O
• Report confidence: X

Result

• Vector string: CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:X
• Score:
  • Base: 2.6
  • Temporal: 2.4
• Severity:
  • Base: Low
  • Temporal: Low

Requirements

• 062.Define standard configurations
• 177.Avoid caching and temporary files
• 266.Disable insecure functionalities
• 349.Include HTTP security headers

Fixes

• Elixir
• Scala
• Python
• Ruby
• Go
• Java
• C-Sharp
• PHP
• TypeScript

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.