On Sat, Feb 2, 2013 at 2:41 PM, Diego Biurrun <[email protected]> wrote:
> On Sat, Feb 02, 2013 at 11:42:05AM +0100, Reinhard Tartler wrote:
>> --- a/src/news
>> +++ b/src/news
>> @@ -1,5 +1,73 @@
>>
>> +<ul>
>> +<li> aacdec: Fix an off-by-one overwrite when switching to LTP profile from 
>> MAIN (CVE-2012-5144) </li>
>> +<li> alsdec: check opt_order (CVE-2012-2775) </li>
>> +<li> alsdec: fix number of decoded samples in first sub-block in BGMC mode 
>> (CVE-2012-2790) </li>
>> +<li> avidec: use actually read size instead of requested size 
>> (CVE-2012-2788) </li>
>> +<li> avsdec: Set dimensions instead of relying on the demuxer 
>> (CVE-2012-2801) </li>
>> +<li> cavsdec: check for changing w/h (CVE-2012-2777 and CVE-2012-2784) </li>
>> +<li> dfa: check that the caller set width/height properly (CVE-2012-2786) 
>> </li>
>> +<li> dfa: improve boundary checks in decode_dds1() (CVE-2012-2798) </li>
>> +<li> indeo4/5: check empty tile size in decode_mb_info() (CVE-2012-2800) 
>> </li>
>> +<li> indeo5: Make sure we have had a valid gop header (CVE-2012-2779) </li>
>
> GOP
>
>> +<li> indeo5: check tile size in decode_mb_info() (CVE-2012-2794) </li>
>> +<li> ivi_common: check that scan pattern is set before using it 
>> (CVE-2012-2791) </li>
>> +<li> lagarith: check count before writing zeros (CVE-2012-2793) </li>
>> +<li> mpeg12: do not decode extradata more than once (CVE-2012-2803) </li>
>> +<li> rv34: error out on size changes with frame threading (CVE-2012-2772) 
>> </li>
>> +<li> vp56: release frames on error (CVE-2012-2783) </li>
>> +<li> wmaprodec: check num_vec_coeffs for validity (CVE-2012-2789) </li>
>
> The spaces before and after the tags seem silly.
>
>> +<p>
>> +Additional, further bugfixes have been made to the following codecs:
>
> bug fixes
>
>> +<li> fix segfault in avformat_open_input() </li>
>> +<li> rtsp: Recheck the reordering queue if getting a new packet </li>
>> +<li> fix uninitialized reads and memory leaks on malformed ogg files </li>
>
> Ogg
>
>> +<p>
>> +We intend to discontinue updates for the 0.7 release branch unless there
>> +is significant demand for an 0.7.8 release. If such an release becomes
>
> s/an/a/
>
>> +necessary in the future, please do not hesitate to get in contact with
>> +us, preferably via email or via an bugzilla entry.
>
> s/an/a/
>
> Push anytime, preferably with the typos corrected.

Thanks for the review, announcement pushed.

-- 
regards,
    Reinhard
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to