update linux libc in hasura image to mitigate CVE-2022-49770#1850
Merged
Conversation
|
Mythicaeda
approved these changes
Jul 14, 2026
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
2 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.
Description
Updates our hasura image to update
linux-libc-devto handle CVE-2022-49770 from recent failing Trivy security scans on the hasura container.Verification
Security scan should pass on this branch. Also you can use this command to check the libc version on a container:
Future work
This is an ad-hoc fix for this particular vulnerability. Long-term we should upgrade the
hasurabase image to a newer version, the one we're using (v2.12.1.cli-migrations-v3) is pretty old