Protect against CRAM compression headers having negative ref_seq_start. #1024
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
This could trigger buffer read overruns in the MD5 calculation code (and perhaps more). Credit to OSS-Fuzz Fixes oss-fuzz 20694
jkbonfield
force-pushed
the
cram_neg_start_fix
branch
from
d09ae40
to
ee06735
Compare
|
Merged as d6f1536 |
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.
This could trigger buffer read overruns in the MD5 calculation code
(and perhaps more).
Credit to OSS-Fuzz
Fixes oss-fuzz 20694