Repository navigation
Conversation
This branch has not been deployed
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
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.
The current 1.2.1 image contains cryptography 46.0.7 (with OpenSSL 3.5.6) and Pillow 12.3.0. Raise the package minimums to cryptography 48.0.1 and Pillow 13.0.0, which include the published security fixes, and update the existing lockfile. Pillow is also brought in by python-roborock's map-parser dependencies, so its minimum must be constrained even though this server does not import it directly.
Refresh installed Debian packages, pull the current Python base in validation/release builds, and fetch the acme.sh 3.1.6 release instead of its moving master branch.
References #235, cryptography's advisory, and Pillow's 13.0.0 security fixes. This confirms dependency versions requiring updates; it does not claim a demonstrated exploitable path in the server.
Validation:
--helpworks.git diff --checkpassed.A new image/app release is still needed to fix installed containers. Both registry tags currently match the image digests running in the affected installation; repulling the existing tag will not update those dependencies. No live server or vacuum state was changed during verification.