Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sensitive values in the logs #39

Open
ehmicky opened this issue Sep 28, 2020 · 3 comments
Open

Sensitive values in the logs #39

ehmicky opened this issue Sep 28, 2020 · 3 comments

Comments

@ehmicky
Copy link
Contributor

ehmicky commented Sep 28, 2020

Does the /api/1/netlify/crawl response include any secure/sensitive values?

The response might be printed by one of the following statements:

console.warn(response);

JSON.stringify(json)

console.error('Could not reach algolia', error);

Netlify build logs are sometimes public, in which case there would be a risk for those sensitive values to be made public as well. However, if this endpoint does not respond with any sensitive values, then this is not a concern. I am raising this up just to be 100% sure :)

@bodinsamuel
Copy link
Contributor

bodinsamuel commented Sep 29, 2020

Netlify build logs are sometimes public

Ah we did not knew that.
We don't output anything more than ids, which are protected by ACL.
But the response error log could leak a token indeed.

@Jerska
Copy link
Member

Jerska commented Sep 29, 2020

Worst case scenario, it will leak the API key. While not ideal, all this gives access to is the ability to trigger a crawl, and I don't see many scenarii where this would be abused maliciously.

@IanVS
Copy link

IanVS commented Nov 22, 2022

This seems fairly important, has it been addressed?

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

No branches or pull requests

4 participants