However the jsonpickle team defended that it is intended. And they suggested that to be sure to be safe, user of this library should set safe=True in calling jsonpickle.decode()https://github.com/jsonpickle/jsonpickle/issues/335
It appears that in indy-plenum, jsonpickle.decode() is called without safe parameter. Wouldn't it be better to add it?
A security guy told me about
indy-node
vulnerabilities. It's aboutjsonpickle
security issue. And it is classified as critical. https://github.com/advisories/GHSA-j66q-qmrc-89rxHowever the
jsonpickle
team defended that it is intended. And they suggested that to be sure to be safe, user of this library should setsafe=True
in callingjsonpickle.decode()
https://github.com/jsonpickle/jsonpickle/issues/335It appears that in
indy-plenum
,jsonpickle.decode()
is called withoutsafe
parameter. Wouldn't it be better to add it?