aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/h264addpx_template.c
diff options
context:
space:
mode:
authorAndreas Rheinhardt <andreas.rheinhardt@gmail.com>2019-06-05 04:18:54 +0200
committerMark Thompson <sw@jkqxz.net>2019-07-20 12:48:18 +0100
commitd4035ca849bdb90e95c87e2737a99ea657be0716 (patch)
tree967d3b6f6002e96e390316915efe98f2e47b92f7 /libavcodec/h264addpx_template.c
parentc104701b6c5db48481fa2fb32b6e3e40b70f1eb6 (diff)
downloadffmpeg-d4035ca849bdb90e95c87e2737a99ea657be0716.tar.gz
cbs_h2645: Fix infinite loop in more_rbsp_data
cbs_h2645_read_more_rbsp_data does not handle malformed input very well: 1. If there were <= 8 bits left in the bitreader, these bits were read via show_bits. But show_bits requires the number of bits to be read to be > 0 (internally it shifts by 32 - number of bits to be read which is undefined behaviour if said number is zero; there is also an assert for this, but it is only an av_assert2). Furthermore, in this case a shift by -1 was performed which is of course undefined behaviour, too. 2. If there were > 0 and <= 8 bits left and all of them were zero (this can only happen for defective input), it was reported that there was further RBSP data. This can lead to an infinite loop in H.265's cbs_h265_read_extension_data corresponding to the [vsp]ps_extension_data_flag syntax elements. If the relevant flag indicates the (potential) occurence of these syntax elements, while all bits after this flag are zero, cbs_h2645_read_more_rbsp_data always returns 1 on x86. Given that a checked bitstream reader is used, we are also not "saved" by an overflow in the bitstream reader's index. Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
Diffstat (limited to 'libavcodec/h264addpx_template.c')
0 files changed, 0 insertions, 0 deletions