How to fix: X-Amz-Cf-Id CloudFront Request ID Exposed
The X-Amz-Cf-Id header exposes an AWS CloudFront request identifier on every response, confirming that CloudFront is in use and leaking request correlation IDs.
Why it matters
Reveals that the site uses AWS CloudFront, which aids attackers in targeting CloudFront-specific misconfigurations (cache poisoning, path-based routing bypass, S3 origin disclosure).
X-Amz-Cf-Id is added by CloudFront to every response for request tracing. While useful for debugging, it leaks CDN infrastructure details to attackers.
How to fix it
- 1Strip X-Amz-Cf-Id using a CloudFront Response Headers Policy.
- 2Or use a Lambda@Edge function to delete the header before sending to the client.
Code examples
CloudFront Response Headers Policy (Terraform)
resource "aws_cloudfront_response_headers_policy" "security" {
name = "strip-internal-headers"
remove_headers_config {
items {
header = "X-Amz-Cf-Id"
}
}
}References
Detected automatically by VulnRadar. The check id is x-amz-cf-id, stable across every scan so you can filter or diff on it.
More config checks
- MediumNo Rate-Limit Policy Detected
- MediumVary: Cookie Missing on Cookie-Bearing Response
- LowSet-Cookie Header Exceeds 4 KB
- LowVary Header Missing on Compressed Responses
- InfoDownloadable Content Served as inline
- InfoX-XSS-Protection Header Is Deprecated
- LowServer-Timing Exposes Cache Timings
- LowVary: Cookie on Static Resource
Questions
- How severe is X-Amz-Cf-Id CloudFront Request ID Exposed?
- VulnRadar rates this info 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 x-amz-cf-id, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Amz-Cf-Id CloudFront Request ID Exposed 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.