Fix subpackage import vulnerability#238
Merged
aymeric-roucher merged 5 commits intomainfrom Jan 17, 2025
Merged
Conversation
albertvillanova
approved these changes
Jan 17, 2025
Member
albertvillanova
left a comment
There was a problem hiding this comment.
Thanks for the security fix.
Closed
Contributor
|
sorry for long wait.. post finally got cleared! wrote up a blog about the technical details on the jailbreak + malicious import. thank you guys for the cooperation and super quick fix :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A malicious LLM could execute malicious code by using subpackages from authorized packages, like this exploiting the fact that
randomis authorized:It required a supply chain attack to have user run a malicious LLM, but it could work.
So this PR fixes it!