Hacker News new | past | comments | ask | show | jobs | submit login

This is an example of how a competent cracker (as opposed to a script kiddie) works. He's:

1) Identified a badly protected side entrance to use rather than the front door

2) Painstakingly researched the third party product (similarly one could investigate a third party library used in a bespoke codebase)

3) Figured out the adaptations the target organisation had made to it and guessed some mistakes they'd made

4) Eventually hit on a cookie modification attack made possible by limitations found in that publicly-available codebase.

Smart.




Let's also add the fact that he reported it so that it can be fixed immediately. :)


While certainly commendable, it does not make the difference between a script kiddie and a competent cracker :)




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: