RE: CR: ASM security vulnerability in rarender.dll
Tad Yeager <[email protected]> Thu, 17 Sep 2009 14:22:50 -0700
| Newsgroups | gmane.comp.multimedia.helix.devel |
|---|---|
| Message-ID | <[email protected]> |
checked into HEAD, Atlas_3_1_0, Atlas_3_4_7, Atlas_3_4_8, Atlas_3_4_9, Cay_1_5_0, Cay_2_4_0, Cay_2_1_0_s, Brizo_4_0_1, Ospreygold. Thanks. At 01:07 PM 9/17/2009, Eric Hyche wrote: >Fix looks good. Please also check into hxclient_3_1_0_atlas and >hxclient_4_0_1_brizo branches. > >Eric > >======================================= >Eric Hyche ([email protected]) >Principal Engineer >RealNetworks, Inc. > > > >-----Original Message----- > >From: [email protected] > [mailto:[email protected]] > >On Behalf Of Tad Yeager > >Sent: Thursday, September 17, 2009 3:52 PM > >To: [email protected]; [email protected] > >Subject: [Helix-client-dev] CR: ASM security vulnerability in rarender.dll > > > >Reported by an outside group, this bug can be triggered by playing back > content with invalid ASM rule > >numbers in the packets. > > > >Per Rishi Matthew's comments on Steve Blanding's fix for a different ASM > rulebook exploit, will > >checkin to HEAD, 347_atlas, 348_atlas, 349_atlas, 210_cays, 150_cay. > > > >Please let me know if this looks OK for checkin. > >Thanks, > >Tad Yeager > >