More of this kind of nuanced, 'teach a person how to ... safely" sort of content, please. Excellent stuff. Thank you.
@ksboi29 Жыл бұрын
Amazing! I was throwing 1 = 1 like noones business!
@dami-vx2215 Жыл бұрын
thanks for this
@UsamaAli-kr2cw Жыл бұрын
Tibirius never disappoints his viewers. Wonderful insights as always keep it up❤❤❤❤❤
@Tib3rius Жыл бұрын
Thanks for the kind words!
@GamesOfficialYouTube Жыл бұрын
@@Tib3rius😂
@shinris3n Жыл бұрын
I "Learned My Lesson" a few months ago thanks to your box on THM 😅
@EliteBuildingCompany Жыл бұрын
Me too lol, pretty fun.
@TCMSecurityAcademy Жыл бұрын
Rock on!
@Saur3n Жыл бұрын
Name of the lab?
@shinris3n Жыл бұрын
@@Saur3n "Lesson Learned"
@brandonbowman6043 Жыл бұрын
Thanks for making this easy to understand. I was hoping for a little more "angry Tibs," but I was happy with the result.
@lowbudgetsinger83333 ай бұрын
very significant knowledge. thank you very much
@M.W.777 Жыл бұрын
Thanks Man!!
@GamesOfficialYouTube Жыл бұрын
Great video
@medhamid8003 Жыл бұрын
Limit 1
@ChristopherMadison Жыл бұрын
Aren't nearly all injection vulnerabilities countered by using parameterized queries? Hasn't that been the standard for many years now? I'm curious how often you've successfully employed SQL injection in production environments recently.
@Tib3rius Жыл бұрын
Developers still have to actively use parameterized queries in order for them to work. Just being a standard isn't enough (something something...nobody follows standards). In other cases, even if developers are using parameterized queries in recent code, if the application is using legacy code, SQL injections may still exist there. I found over 100 SQL injections in 2023 alone.
@alexgreen176710 ай бұрын
Haha, what a rebuttal. Sudo apt install return burn.
@PhantomWorksStudios Жыл бұрын
Cant this be negated by using the functions that will escape special chars?? And cant we make our own function if it comes down to it to sterlize " and ' into html hex counterparts from the ascii table?
@Tib3rius Жыл бұрын
Are you talking about ways to mitigate SQL injection itself? If so, prepared statements are the recommended way to go rather than manually escaping / sanitizing characters.