Skip to main content
LowConfigOWASP A05:2021CWE-200

How to fix: Server-Timing Exposes Cache Timings

Server-Timing values such as cache;dur=12 or edge;dur=4 expose internal cache hit/miss timing to the client and to any cross-origin page with a Timing-Allow-Origin grant.

Why it matters

Cache timing data reveals whether a URL is in the cache, which can be used to infer which users have visited a page (cache probing attack) and to fingerprint backend architecture (Varnish, Redis, CDN HIT/MISS patterns).

Server-Timing carries per-request performance metrics. Cache duration entries (cache;dur=..., hit;dur=0, miss;dur=200) reveal the caching topology. An attacker with access to timing data can infer user browsing patterns by checking whether a URL is cached.

How to fix it

  1. 1Strip Server-Timing at the edge for public responses.
  2. 2If you need Server-Timing for monitoring, gate it behind Timing-Allow-Origin with a specific trusted origin, not '*'.
  3. 3In Nginx: proxy_hide_header Server-Timing;

Code examples

Nginx: strip Server-Timing

nginx
proxy_hide_header Server-Timing;
proxy_hide_header Timing-Allow-Origin;

References

Detected automatically by VulnRadar. The check id is server-timing-cache-timings, stable across every scan so you can filter or diff on it.

See every config check

Questions

How severe is Server-Timing Exposes Cache Timings?
VulnRadar rates this low severity in the config category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id server-timing-cache-timings, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Server-Timing Exposes Cache Timings map to?
It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for server-timing exposes cache timings

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Server-Timing Exposes Cache Timings | VulnRadar