HSEC-2023-0001: aeson hash flooding #35
Merged
Conversation
This file contains 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
frasertweedale
force-pushed
the
adv/aeson-hash-flooding
branch
from
5f819ce
to
fd32813
Compare
blackheaven
approved these changes
Jun 13, 2023
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.
Add aeson hash flooding advisory.
This should put our CI through its paces. Some other things to note/discuss:
advisories/hackage/<package-name>?HSECidentifier, because they'll be spread across different directories. (ci: check HSEC id uniqueness #38)HSECidentifier? If so, we should (eventually) extend the checks to make sure that the ID in the TOML header matches the filename. (check HSECidmatches filename #40)Later, we could add merge automation to select the next appropriate
HSECidentifier and update the commit before merging. It's a "nice to have" and we can do it later.