How to fix: AWS S3 NoSuchBucket error pattern exposed
S3 bucket hosting returned a 'NoSuchBucket' or 'AccessDenied' XML error response, revealing the bucket name, region, and an x-amz-request-id header that can be correlated with AWS account activity.
Why it matters
S3 error responses expose the bucket name and region, enabling bucket name enumeration and subdomain takeover attempts on deleted or unclaimed buckets. The x-amz-request-id can be used alongside AWS support channels to correlate requests with account activity. AccessDenied responses also confirm that a bucket exists at the given name.
When a static site is served directly from an S3 bucket hostname, any error (missing file, wrong bucket name, or access control failure) returns an XML-formatted AWS error document. These responses confirm the bucket name, region endpoint, and the presence of the AWS account in the S3 namespace.
How to fix it
- 1Front S3 with CloudFront or another CDN that intercepts and rewrites error pages.
- 2Configure CloudFront custom error responses for 403 and 404 to serve generic HTML.
- 3Disable direct bucket hostname access via bucket policies that deny s3.amazonaws.com Origin requests.
- 4Use a vanity domain backed by CloudFront rather than exposing bucket hostnames.
Code examples
CloudFront (custom error response via Terraform)
resource "aws_cloudfront_distribution" "site" {
# ... origin config ...
custom_error_response {
error_code = 403
response_code = 404
response_page_path = "/404.html"
}
custom_error_response {
error_code = 404
response_code = 404
response_page_path = "/404.html"
}
}S3 bucket policy (deny direct bucket access)
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "cloudfront.amazonaws.com"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::my-bucket/*",
"Condition": {
"StringEquals": {
"AWS:SourceArn": "arn:aws:cloudfront::123456789012:distribution/EDFDVBD6EXAMPLE"
}
}
}
]
}References
Detected automatically by VulnRadar. The check id is aws-s3-nosuchbucket-error, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is AWS S3 NoSuchBucket error pattern exposed?
- VulnRadar rates this low severity in the info disclosure 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 aws-s3-nosuchbucket-error, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does AWS S3 NoSuchBucket error pattern exposed map to?
- It maps to CWE-209. 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.