Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More CRAM fuzz fixes (integer overflows) #1713

Merged
merged 2 commits into from
Dec 4, 2023
Merged

More CRAM fuzz fixes (integer overflows) #1713

merged 2 commits into from
Dec 4, 2023

Commits on Dec 4, 2023

  1. Avoid undefined behaviour integer overflow in extend_ref 

    Credit to OSS-Fuzz
Fixes oss-fuzz 64646
    @jkbonfield
    jkbonfield committed Dec 4, 2023
    Configuration menu
    Copy the full SHA
    24dab0c View commit details
    Browse the repository at this point in the history

  2. Fix integer overflow in cram_compress_block2 

    The figure used here is somewhat arbitrary as it's simply a marker for
something considerably worse than no compression, given it's used in
places where the compression wasn't applied or fails.  Although sz is
long, it may get other modifiers and the CRAM block size is int so
UINT_MAX seems like a natural "larger than possible" value to use.

Credit to OSS-Fuzz
Fixes oss-fuzz 64616
    @jkbonfield
    jkbonfield committed Dec 4, 2023
    Configuration menu
    Copy the full SHA
    ba18cb9 View commit details
    Browse the repository at this point in the history