Attack and defence in web games: a structured overview
A tour of the recurring weak points in browser-based games: tamperable network protocols, memory edits, save-file edits, and account or payment fraud.
Read moreHome / Archive: 2012
Notes first published in 2012.
A tour of the recurring weak points in browser-based games: tamperable network protocols, memory edits, save-file edits, and account or payment fraud.
Read moreA look at activity hijacking: a non-root Android technique where a malicious app watches for a target app, then overlays a convincing fake login screen.
Read moreA legacy Novell/ConsoleOne environment illustrates how group self-enrolment and concurrent sessions turn modest access into full account takeover.
Read moreA tour of the anti-debugging tricks in Hack.lu's mealtime CTF binary: PEB-flag checks, deferred VEH registration, and injection across two processes.
Read moreOverview of how testers historically got around single-character filtering and browser XSS filters, and what it taught defenders about input handling.
Read moreHow an old PHP input-escaping feature changed request content in a way a browser's XSS filter did not account for, allowing a bypass.
Read moreA firmware-analysis CTF challenge solved by identifying the device, extracting its filesystem, and locating a flag file inside it.
Read moreA CTF binary challenge shipped a packet capture plus an executable for an unfamiliar architecture, solved mainly through protocol-flow reasoning.
Read moreMimikatz showed that lsass.exe held reversibly encrypted credentials, not just hashes, and that discovery reshaped how Windows protects memory.
Read moreApache's handling of oversized headers once echoed full cookie values back in an error page, defeating the httponly flag that was meant to hide them from scripts.
Read moreA reported flaw in a CMS's upload component showed how outsourcing an upload widget's front end can leave its backend endpoint unchecked.
Read moreExploiting the Apache cookie-disclosure flaw needed a second weaker XSS, not a direct document.cookie read, to push the cookie jar over the server's size limit.
Read more