Posted: 9/12/2016 5:25 PM
Post subject: VBA vulnerability
Quote
Memory
She/Her
Site Admin, Skilled player (1523)
Joined: 3/20/2014
Posts: 1762
Location: Dumpster
GBA TASer of 2020 GBA TAS of 2020 GBA TASer of 2019 Exotic platforms TAS of 2018
Link to video Video explains everything. This explicitly includes VBA-RR which is still supported on the site.
[16:36:31] <Mothrayas> I have to say this argument about robot drug usage is a lot more fun than whatever else we have been doing in the past two+ hours
[16:08:10] <BenLubar> a TAS is just the limit of a segmented speedrun as the segment length approaches zero
Posted: 9/12/2016 7:35 PM
Quote
MUGG
Editor, Expert player (2313)
Joined: 5/15/2007
Posts: 3855
Location: Germany
Gameboy TASer of 2015 NES TAS of 2013 Gameboy TASer of 2011 Gameboy TASer of 2010
VBA-rr 1.7.2 and 1.8 are stone age old. I haven't heard of those since 2008. VBA-rr 19~23, I'm not sure if those are still supported. I'm under the impression they have emulation inferior to VBA 24m's (so we could probably safely deprecate those versions). Do those versions have the exploit? Oh I see now. ALL versions have that problem.
Youtube • Livestream • Progress 11th TASer of the Decade 2010-2019 !
Posted: 9/15/2016 10:39 AM
Quote
klmz
Editor, Emulator Coder, Expert player (2105)
Joined: 5/22/2007
Posts: 1134
Location: Glitchvania
NES TASer of 2018 GBA TASer of 2018 GBA TAS of 2016 Lucky TAS of 2016 GBx TASer of 2008 NES TAS of 2007
Thanks for the report. I fixed it altogether with a similar issue wiht the "Cheat List" loading yesterday in VBA-rr. I'd like to fix one more issue before I publish a new "release" though. EDIT: It has been fixed.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days <adelikat> no doubt <adelikat> klmz, they still do
Posted: 11/4/2016 7:43 AM
Quote
endrift
Any
Emulator Coder
Joined: 12/14/2014
Posts: 161
I have two additional vulnerabilities in VBA (one of which has been fixed upstream as of yesterday, the other I just reported) that should probably get merged downstream as well. I can PM a maintainer details if they want to fix it; I don't want to leave the details out in the open before it's patched though.