-
Notifications
You must be signed in to change notification settings - Fork 525
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
v5.2 fails to load serialized exception with load(handle, Loader=yaml.FullLoader
#364
Comments
Yes it is.
|
frdeso
added a commit
to frdeso/lttng-ci
that referenced
this issue
Dec 20, 2019
Since PyYAML version 5.2 `load()` errors out when parsing such field: !!python/object/apply:collections.OrderedDict [...] This is done to prevent vulnerabilities exploitable using the `object/apply` construct. See this Github issue [1]: I believe the real bug is that Lava produce a yaml file with such a construct. I believe it's not on purpose because we can see a commit [2] preventing the use of `object/apply` for another type. For now, use `unsafe_load()` until lava does not produce `object/apply` contructs. [1] yaml/pyyaml#364 [2] Linaro/lava@14b347c Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
frdeso
added a commit
to frdeso/lttng-ci
that referenced
this issue
Dec 20, 2019
Since PyYAML version 5.2 `load()` errors out when parsing such field: !!python/object/apply:collections.OrderedDict [...] This is done to prevent vulnerabilities exploitable using the `object/apply` construct. See this Github issue [1]: I believe the real bug is that Lava produce a yaml file with such a construct. I believe it's not on purpose because we can see a commit [2] preventing the use of `object/apply` for another type. For now, use `unsafe_load()` until lava does not produce `object/apply` contructs. [1] yaml/pyyaml#364 [2] Linaro/lava@14b347c Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
PSRCode
pushed a commit
to lttng/lttng-ci
that referenced
this issue
Dec 20, 2019
Since PyYAML version 5.2 `load()` errors out when parsing such field: !!python/object/apply:collections.OrderedDict [...] This is done to prevent vulnerabilities exploitable using the `object/apply` construct. See this Github issue [1]: I believe the real bug is that Lava produce a yaml file with such a construct. I believe it's not on purpose because we can see a commit [2] preventing the use of `object/apply` for another type. For now, use `unsafe_load()` until lava does not produce `object/apply` contructs. [1] yaml/pyyaml#364 [2] Linaro/lava@14b347c Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider the following dump/load round trip where we serialize an exception:
This works fine with
pyyaml~=5.1.0
however it fails for v5.2 with the following exception:Is this difference in behavior expected?
The text was updated successfully, but these errors were encountered: