MonsterYT_DaGamerLvl 8
- Android
DragonFireGames oh yes, that explains everything
DragonFireGames oh yes, that explains everything
MonsterYT_DaGamer Short summary, I can block inspect console & data browser at the same time.
Give. Now.
[WUT] Adam Now, here is the problem, it gives you TOTAL access to all of the inspect console from within a gamelab project. You can execute scripts on the behalf of anyone running the project. I can create a project which when run will replace your projects with copies of that project and publish them. Do you understand the security issue this presents?
A proper demonstration of it's power.
EDIT: Removed video since it don't work
DragonFireGames Video won't play for me :(
Jibberjay unfortuante :)
DragonFireGames imma need that
If i had coins i would give
imreallyhuman don't you have 1.6 coins
I've decided to report it as a bug to code.org since I realize the devastating potential of an exploit like this. For now, I shall wait until it is patched. Cry about it, but it's the responsible thing to do.
imreallyhuman
owokoyo pfp crazy
DragonFireGames Damn 😔
but that is the responsible thing to do ngl
DragonFireGames thats not good
DragonFireGames Did CDO ever respond or fix it? And would it be any less dangerous with the new gallery preventing publishing?
Binary_Coder Nope, never happened, and yes it is less dangerous without public project publishing.
The main issue with the vulnerability is that it allows projects to run scripts that can literally delete or edit projects in your account. I could make a project, that, when run, copies it's source code to all of your projects and then auto publishes them to the public gallery, propagating the worm across cdo wiping millions of projects.
DragonFireGames such power
If someone was good enough I’m sure that your inspect console blocker wouldn’t work against them.
SquirrelGuy-5 but I bet they’d have to be real good