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

security issues in rencode #1217

Closed
totaam opened this issue Jun 3, 2016 · 4 comments
Closed

security issues in rencode #1217

totaam opened this issue Jun 3, 2016 · 4 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Jun 3, 2016

Just reported two security issues in rencode:

For our use case, I believe this can just cause a server crash, I don't think we leak parsed data from packets back to the user - but maybe disconnection messages? (those would need to be trimmed)

@totaam
Copy link
Collaborator Author

totaam commented Jun 9, 2016

The first bug is now fixed and version 1.0.5 will include it, the second one was already fixed in rencode 1.0.4. (my bad)

Until 1.0.5 is officially released (new blocker: [https://github.com/aresch/rencode/issues/9]), here's a download link: [https://github.com/aresch/rencode/archive/a5ab0fb6c3603d1e9c53e2cfc262b2288d2912d8.zip].

@totaam
Copy link
Collaborator Author

totaam commented Jul 16, 2016

This is all fixed in version 1.0.5, bumped for osx and rpm in r13028. (r13029 for centos6 because of this bug: [https://github.com/aresch/rencode/issues/10])

@smo: time to update.

@totaam
Copy link
Collaborator Author

totaam commented Aug 2, 2016

  • r13120 updates the debian repos to use 1.0.5
  • r13129 removes rencode from our source tree

@totaam
Copy link
Collaborator Author

totaam commented Aug 11, 2016

2016-08-11 17:37:16: smo commented


All updated.

@totaam totaam closed this as completed Aug 11, 2016
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

1 participant