How to fix: ETag reveals server inode number
The ETag header format suggests it includes a file inode number, potentially revealing internal server file system details.
Why it matters
inode-based ETags leak the file's inode number on the server, which can be used to identify server software, configuration, and in some cases to correlate requests across virtual hosts sharing the same filesystem.
Apache's default ETag format includes inode, file size, and modification time. Configure it to exclude the inode.
How to fix it
- 1Apache: FileETag MTime Size (removes inode)
- 2Nginx generates ETags from last-modified time and content length, no inode included by default
Code examples
Apache: remove inode from ETag
# In httpd.conf or .htaccess:
FileETag MTime Size
# The default "FileETag All" includes inode; this removes itReferences
Detected automatically by VulnRadar. The check id is etag-inode, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is ETag reveals server inode number?
- 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 etag-inode, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does ETag reveals server inode number 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.