-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
LazyFrame.deserialize() should document the security implications #14623
Labels
Comments
douglas-raillard-arm
added
the
documentation
Improvements or additions to documentation
label
Feb 21, 2024
Can you make a PR? |
I'm following my employer's legal process to be able to contribute to polars, after that I should be able to make a PR. I'm currently discovering the API and exploring how I can use it best for our use case, hence all the issues I opened recently :) |
douglas-raillard-arm
added a commit
to douglas-raillard-arm/polars
that referenced
this issue
Mar 25, 2024
Add indication that LazyFrame.deserialize() might execute arbitrary code coming from the deserialized data. Fixes pola-rs#14623
Here we go: #15282 |
douglas-raillard-arm
added a commit
to douglas-raillard-arm/polars
that referenced
this issue
Apr 2, 2024
…r.deserialize() docstring Add indication that LazyFrame.deserialize() and Expr.deserialize() might execute arbitrary code coming from the deserialized data. Fixes pola-rs#14623
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Since LazyFrame.deserialize() can end up calling into pickle/cloudpickle, it makes it unsafe to use on non-trusted input, so it would be good if it stated it similarly to the Python doc:
Link
https://docs.python.org/3/library/pickle.html
https://docs.pola.rs/py-polars/html/reference/lazyframe/api/polars.LazyFrame.deserialize.html
The text was updated successfully, but these errors were encountered: