How to fix: ETag value may contain inode information
The ETag response header contains a value that appears to embed inode numbers from the server filesystem.
Why it matters
Exposing inode numbers helps attackers fingerprint the exact web server software version and may reveal filesystem structure that aids in targeted path traversal or LFI attacks.
Change Apache's ETag configuration to exclude inode values.
How to fix it
- 1Apache: "FileETag MTime Size" in httpd.conf or .htaccess removes inode from ETags
- 2Alternatively, disable ETags entirely: "FileETag None"
Code examples
Apache: disable inode in ETags
FileETag MTime Size
# Or disable ETags entirely if not needed:
# FileETag None
# Header unset ETagReferences
Detected automatically by VulnRadar. The check id is etag-inode-leak, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is ETag value may contain inode information?
- 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-leak, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does ETag value may contain inode information 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.