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

http security issue #1844

Closed
mandric opened this issue Jan 25, 2016 · 1 comment
Closed

http security issue #1844

mandric opened this issue Jan 25, 2016 · 1 comment
Labels
Type: Bug Fix something that isn't working as intended Won't fix: Ancient Too old to investigate

Comments

@mandric
Copy link
Contributor

mandric commented Jan 25, 2016

No description provided.

@mandric
Copy link
Contributor Author

mandric commented Feb 9, 2016

Dev branches have been patched and issue opened upstream apache/nano#311.

garethbowen pushed a commit that referenced this issue Oct 24, 2017
Added a `db.sanitizeResponse` that can be called from any controller.  The only
problematic function right now is `forms.getForm` because it returned headers
coming from nano.  Sanitized those headers by removing `uri` and `statusCode`
and wrote tests around it.  This could potentially leak auth information to the
client.  See https://github.com/dscape/nano/blob/master/lib/nano.js#L195

TODO: open issue in nano project and patch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Fix something that isn't working as intended Won't fix: Ancient Too old to investigate
Projects
None yet
Development

No branches or pull requests

3 participants