How to fix: Server-Timing exposes sensitive key
The Server-Timing response header includes custom keys that may expose internal metrics like db, sql, redis, cache, or query durations.
Why it matters
Drop or sanitize Server-Timing entries with sensitive names in production
The Server-Timing response header includes custom keys that may expose internal metrics like db, sql, redis, cache, or query durations.
How to fix it
- 1Drop or sanitize Server-Timing entries with sensitive names in production
Code examples
Remove sensitive metric names from Server-Timing
// BAD: Server-Timing: db;dur=150, cache-miss;dur=5
// Reveals internal architecture: database, cache layer
// GOOD: use opaque names or omit timing in production
const timings: string[] = [];
if (process.env.NODE_ENV !== "production") {
timings.push(`db;dur=${dbMs}`);
}
if (timings.length) res.setHeader("Server-Timing", timings.join(", "));References
Detected automatically by VulnRadar. The check id is server-timing-sensitive-key-leak, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Server-Timing exposes sensitive key?
- VulnRadar rates this low severity in the headers 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-sensitive-key-leak, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server-Timing exposes sensitive key 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.