Skip to main content

How to fix: Server-Timing Exposed Without Timing-Allow-Origin Gate

Server-Timing is exposed publicly without a Timing-Allow-Origin restriction, allowing any cross-origin page to read performance data.

Why it matters

Cross-origin attackers can read precise timing data and fingerprint the backend stack, infer database query counts, and mount cache-probing attacks to detect which pages a user has visited.

Server-Timing carries per-request performance metrics. When exposed without a Timing-Allow-Origin restriction, the browser sends it to the cross-origin document and any timing-based fingerprinting attack can run.

How to fix it

  1. 1Hide Server-Timing at the edge (proxy_hide_header Server-Timing) for public responses.
  2. 2If you need to expose it for monitoring, set Timing-Allow-Origin to a specific trusted origin instead of '*'.
  3. 3Strip cache;dur, db;dur, edge;dur style entries that reveal backend internals.

Code examples

Nginx

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

Restrict to trusted origin

HTTP
Timing-Allow-Origin: https://monitoring.internal.example.com

References

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

See every config check

Questions

How severe is Server-Timing Exposed Without Timing-Allow-Origin Gate?
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-allow-origin-public, which stays the same between runs so you can filter, diff, or gate CI on it.

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 exposed without timing-allow-origin gate

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

Server-Timing Exposed Without Timing-Allow-Origin Gate | VulnRadar