That ruleset means two things:
First, everyone can read not only every part of your database, but the whole database at once. Even if everything stored might as well be public information, this means that someone could access the root node and download everything in one operation. Depending on the size of your database, this might at least lead to a huge bill for you down the line, even if you believe that getting to know the URL to every single image and video of yours is not a problem.
Second it means that every authenticated user can write anything to any location in your database. This allows stuff like changing individual video URLs to any other video URL that may exists somewhere on the internet and which will subsequently be shown to your users as if it was your content, but also stuff like just writing a null value to your root node and deleting everything you've got.
Neither option sounds really secure to me, so you should do at least two things: restrict read operations to individual nodes further down the tree (depending on what structure makes sense for you), and restrict write operations not just to any authenticated user, but to specific user accounts that you control.