Sensitive Content Cacheable

Pages or API responses containing sensitive data are sent without directives that stop browsers and intermediate caches storing them, so copies may be recovered later.

SeverityLow
CVSS 3.12.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.02.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-525: Use of Web Browser Cache Containing Sensitive Information
OWASP Top 10A06:2025 Insecure Design
MITRE ATT&CKT1005 Data from Local System
CategorySecurity Misconfiguration

Description

Responses that contain sensitive information, such as account details, personal or financial data or authenticated API output, are sent without caching directives that prevent them being stored, or with directives that allow it, such as Cache-Control: public or a long max-age. Browsers may then keep copies in their disk cache, and shared caches, such as corporate proxies or content delivery networks that can see the traffic, may store them too.

Copies in a browser's cache remain after the user logs out, so a person who later uses the same computer and browser profile, for example on a shared, public or kiosk machine, or who obtains the cache files from disk, can read sensitive pages that a previous user viewed. A shared cache that stores an authenticated response may serve it to other users of that cache, giving them one user's data. The impact depends on what the cached responses contain and where the application is used: it is greatest for applications used on shared or public computers and low where users have their own managed devices.

The issue is identified by reviewing the Cache-Control, Expires and Pragma headers on authenticated responses, and by logging out and then inspecting the browser's cache or using the back button to see whether sensitive pages are shown again. Scanners report it as cacheable HTTPS responses.

Remediation

Mark every response that contains sensitive or user-specific data so that caches do not store it:

  • Send Cache-Control: no-store on authenticated pages, API responses containing personal or sensitive data, and downloads of such data. Where old HTTP/1.0 caches must be allowed for, also send Pragma: no-cache and Expires: 0.
  • Where a response may be kept by the browser but never by a shared cache, use Cache-Control: private. Use no-cache only where revalidation before each use is the intention, since it still allows storage.
  • Set caching headers for authenticated routes as a whole in the application or framework, rather than page by page, while leaving static public assets cacheable.
  • Configure any content delivery network or reverse proxy not to cache responses to authenticated requests.
  • Consider sending Clear-Site-Data: "cache" when a user logs out.
Cache-Control: no-store

Confirm the fix by checking the headers on authenticated responses and that, after logging out, sensitive pages are not shown from the browser's cache.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding