--Originally published at Eric tries to write down cool things
If I had to pick 1 topic to be my favorite from the mastery topics list, this one would win and by far.
Why do I think it’s the best one? Welllll, we like to screw up OVER AND OVER!
Most of security issues come from unintentional implementations. Badly written code, bad implementation of restrictions, too much information given away to unnecessary users, showing your code to your mom.
Really! Damn! There is so much to screw up all over the damn place! It’s just impossible to cover every single security scenario. The best you can do as a security brigadier is to implement and think of all the things you are capable of. Think of every single mother effing scenario that you can think that can go wrong. You won’t cover all of them, but oh boy will you try and make things better!
We covered a lot of issues in class demonstrating how things were badly made. For example, Isaac purchased some buss ticked online to go to Tepic, but he didn’t receive the tickets, so he YOLOed and went into the console and started looking for answers… AND OH BOY HE FOUND THEM! He found the source code of many things that could’ve compromised the information of other users aboard the bus and he could resubmit other information into the webpage, making a huge security issue.
And now, do we really think that the engineer from this site made this on purpose? Let’s damn hope he didn’t, if he did, well what a damn ass.
He didn’t expect that a mortal like Isaac would go in the chrome console to look for answers. This was the programmer’s demise, to think there were no other gods aside from him.
So remember kids! Try to break your stuff
Continue reading "Unintentional Security Issues. WOOPS!"