-
Notifications
You must be signed in to change notification settings - Fork 167
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
CVE-2014-3539 python-rope: pickle.load of remotely supplied data with no authentication #105
Comments
I am aware of it, and I was working on it https://gitorious.org/rope/rope/source/CVE-2014-3539 but I have never been able to pull off a good automatized reproducer for test. Any merge requests for that branch would be very very welcome. |
Hi, I'm a fan of rope, but am concerned about using it due to this issue. I'm wondering if you might be willing to share your current thinking? Thanks. In case it's helpful, Debian seems to have a limited patch. |
Hi, I know this has been sitting for far too long. I am working on the fix for this issue. |
I have a proposed fix in #251. I'm not sure who will review it who is very familiar with this codebase (or if there is such a person anymore). This does need to be resolved, so I will get at least another competent pair of eyes on it. Please anyone take a look as well if you are interested. |
Given the authorship of last commits to |
…ts (#251) Perform signature verification on pickled data transferred over sockets Before unpickling anything, ensure that it has a valid digital signature using a randomly-generated shared key. In order for an attacker to send or tamper with data on the same socket, they must know this key to compute a valid signature. Fixes #105, CVE-2015-3539.
https://bugzilla.redhat.com/show_bug.cgi?id=1116485
The text was updated successfully, but these errors were encountered: