| Management number | 233621896 | Release Date | 2026/06/27 | List Price | US$8.36 | Model Number | 233621896 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
Seemingly simple bugs can have drastic consequences, allowing attackers to compromise systems, escalate local privileges, and otherwise wreak havoc on a system.A Bug Hunter's Diary follows security expert Tobias Klein as he tracks down and exploits bugs in some of the world's most popular software, like Apple's iOS, the VLC media player, web browsers, and even the Mac OS X kernel. In this one-of-a-kind account, you'll see how the developers responsible for these flaws patched the bugs—or failed to respond at all. As you follow Klein on his journey, you'll gain deep technical knowledge and insight into how hackers approach difficult problems and experience the true joys (and frustrations) of bug hunting.Along the way you'll learn how to:–Use field-tested techniques to find bugs, like identifying and tracing user input data and reverse engineering–Exploit vulnerabilities like NULL pointer dereferences, buffer overflows, and type conversion flaws–Develop proof of concept code that verifies the security flaw–Report bugs to vendors or third party brokersA Bug Hunter's Diary is packed with real-world examples of vulnerable code and the custom programs used to find and test bugs. Whether you're hunting bugs for fun, for profit, or to make the world a safer place, you'll learn valuable new skills by looking over the shoulder of a professional bug hunter in action. Read more
| ASIN | B00652XO2I |
|---|---|
| XRay | Not Enabled |
| ISBN13 | 978-1593274153 |
| Edition | 1st |
| Language | English |
| File size | 4.0 MB |
| Page Flip | Enabled |
| Publisher | No Starch Press |
| Word Wise | Not Enabled |
| Print length | 200 pages |
| Accessibility | Learn more |
| Screen Reader | Supported |
| Publication date | October 11, 2011 |
| Enhanced typesetting | Enabled |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form