Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Catch arrays of BCF_BT_NULL in bcf_record_check()
Adds a check for INFO/FORMAT values with type 0 ("A MISSING value without an explicit type provided") and number of elements > 0. Normally type = 0 and number = 0 is used for a completely missing INFO/FORMAT value. In theory you could use number > 0 to make an array of missing values (at least the specification doesn't explicitly disallow it), however trying to do so results in bcf_fmt_array() reporting "Unexpected type 0" and calling exit(1). HTSJDK also appears to reject this encoding, and nothing appears to write it, so it seems reasonable to say that it's not valid. The check for this encoding is added to bcf_record_check() so it's caught well before the data gets near bcf_fmt_array(). It also avoids problems with bcf_type_shift[], which cannot report the correct size of type = 0 encodings (it would need to multiply by 0, which isn't stricty possible with a shift). Credit to OSS-Fuzz Fixes oss-fuzz 49091
- Loading branch information