Skip to content

feat: redact GCS error messages in HTTP responses - #67

Open
kaiburjack wants to merge 1 commit into
daichirata:masterfrom
kaiburjack:feat/redact-error-responses
Open

feat: redact GCS error messages in HTTP responses#67
kaiburjack wants to merge 1 commit into
daichirata:masterfrom
kaiburjack:feat/redact-error-responses

Conversation

@kaiburjack

Copy link
Copy Markdown

Currently, whenever GCS responds with 404 due to an object in a bucket not existing, the full GCS bucket/object path is mentioned in the response.
This has security implications for gcsproxy deployments that are being served publicly, like we do behind a CDN. These information can be used by malicious actors to enumerate buckets and objects within buckets and access permissions of the GCS service account against those buckets.

In our own gcsproxy fork redact all information from the 404 and 500 response bodies to not reveal these information. There is still an option to log the errors, though, to see whether anything suspicious is going on.

This PR adds a flag to redact error bodies from responses and to toggle logging of such error messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant