-
Notifications
You must be signed in to change notification settings - Fork 370
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
Questions about vulnerabilities in Indy Plenum dependencies #1680
Comments
There are significant changes in the ujson library from 1.33 to a version that doesn't contain a vulnerability.
The ujson impacts the following files:
The calls inside of Indy Plenum to ujson include
Testing possible upgrade path.
It appears that the interfaces between ujson versions has been maintained, and it may simply involve upgrading the version of ujson to use a version that doesn't have the vulnerability. It may also be possible to use the native Python json libary, as the Indy Plenum calls include falling back to the json library. This would allow us to simply drop the use of ujson if desired.
|
Thanks. Any idea if the ujson High vulnerability issue is being used in Plenum, or is the vulnerability description insufficiently detailed to determine that? |
What is the impact of these vulnerabilities on the currently released version of Indy Plenum?
The text was updated successfully, but these errors were encountered: