undrgrnd Cliquez ici Toys NEWNEEEW nav-sa-clothing-shoes nav-sa-clothing-shoes Cloud Drive Photos cliquez_ici Rentrée scolaire Cliquez ici Acheter Fire Shop Kindle Paperwhite cliquez_ici Jeux Vidéo Bijoux Montres Montres boutique Tendance
A Bug Hunter's Diary et plus d'un million d'autres livres sont disponibles pour le Kindle d'Amazon. En savoir plus
  • Tous les prix incluent la TVA.
Il ne reste plus que 4 exemplaire(s) en stock (d'autres exemplaires sont en cours d'acheminement).
Expédié et vendu par Amazon. Emballage cadeau disponible.
Quantité :1
A Bug Hunter's Diary - A ... a été ajouté à votre Panier
+ EUR 2,99 (livraison)
D'occasion: Comme neuf | Détails
Vendu par SuperBookDeals..
État: D'occasion: Comme neuf
Commentaire: Remboursement garanti à 100%. Etat neuf, expédition rapide sous 4 à 14 jours ouvrés. Plus d'un millions de clients servis. Service à la clientèle en Français.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

A Bug Hunter's Diary - A Guided Tour Through The Wilds of Software Security (Anglais) Broché – 4 novembre 2011

Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
"Veuillez réessayer"
EUR 37,18
EUR 24,69 EUR 24,84

Livres anglais et étrangers
Lisez en version originale. Cliquez ici

Descriptions du produit

A Bug Hunter's Diary Klein tracks down and exploits bugs in some of the world's most popular programs. Whether by browsing source code, poring over disassembly, or fuzzing live programs, readers get an over-the-shoulder glimpse into the world of a bug hunter as Klein unearths security flaws and uses them to take control of affected systems. Full description

Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone

Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.

Détails sur le produit

En savoir plus sur l'auteur

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Quels sont les autres articles que les clients achètent après avoir regardé cet article?

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 29 commentaires
14 internautes sur 14 ont trouvé ce commentaire utile 
To the point 8 novembre 2011
Par Happy Cat - Publié sur Amazon.com
Format: Broché
This was a great read; short and focused. While it did not have as much variety as other books, such as The Art Of Software Security Assessment, Bug Hunter's Diary had little or no fluff and was filled with valuable content.

In each chapter, the author did a great job walking through identifying the vulnerability, and explaining the thought process in a digestible, straightforward manner. The brief enumeration of possible disclosure routes was also worded well to concisely explain why a bug hunter might pursue each avenue. Lastly, it was good to see the author track the remediating patch and identify the resulting vulnerabilities.

Tobias Klein is very thorough and detailed in his discovery of vulnerabilities, but in a concise manner. He sticks right to the point and keeps on track for honing in on vulnerable code and triggering said code with the proper conditions and data.

It was also amusing to compare differences in the disclosure timelines from chapter to chapter. Independent, open source targets were patched much more quickly than their counterparts that were fostered by larger organizations. It is uncertain as to whether this was an intentional observation, but interesting none-the-less.

This is a short, fun read for anyone who is interested in vulnerability analysis and exploit development.
9 internautes sur 9 ont trouvé ce commentaire utile 
Exceptional 17 novembre 2011
Par Gregory Zentkovich - Publié sur Amazon.com
Format: Broché
There is a wealth of knowledge being passed in this easy to follow along book. Although some of the content (i.e. the source code), might seem cryptic at first, Tobias does an excellent job of going out of his way to making it understandable. In one instance, he was breaking down some assembly code and used pseudo c code to make it more understandable, and almost as if he could see my eyes still glazing over, he simplifies even further with pseudo code that was language-neutral (basically english), and then the light bulb went on. I was amazed at what I was learning. I also liked the fact that I did not have to concern myself or be distracted from the process because I did not understand some code, and that was huge. In addition, he has a lot of great visual diagrams, side notes, links to source code and the tools used, references for further study, basically the whole shebang. Simply put, Tobias made my first journey into the world of bug hunting an exciting one. I would highly recommend this to anyone who wants to better their programming skills, get into computer security research or just plain understand how software works this book will get you jump started and excited!
8 internautes sur 8 ont trouvé ce commentaire utile 
Ask Felgall - Book Review 29 novembre 2011
Par Stephen Chapman - Publié sur Amazon.com
Format: Broché
A read of this book may change your view of computer software forever. The real world security holes that it discusses were found in extremely popular software on a variety of different platforms and clearly represent only a few samples of such holes that are common across most software.

While a fairly advanced level of programming knowledge both with high level languages such as C++ and also with low level assembly language is required to be able to fully understand just exactly how everything described in the book works, it isn't necessary to have that in depth knowledge in order to gain some benefit. Since the purpose of each code change is described in detail in the book those without such an in depth programming knowledge can simply take the author's word for it that a given code change will have a particular result and will still be able to gain a greater understanding of just how vulnerable software can be. These are after all real vulnerabilities that the author found in common software that have since been patched. So as well as demonstrating some of the ways in which holes can be found and exploited the author also demonstrates how he has contributed to helping the owners of this software to patch some of the holes in their software and so make the software safer to use.

Perhaps the things that most stand out about software security from this book are first of all just how easily some security holes can be found by someone who has sufficient experience in "bug hunting" and second, just how small a code change is needed in many instances in order to fix these security holes.

In the front of the book the author describes the goals that he had in writing the book and the book definitely achieves those goals. One comment from the author particularly stood out as I read through the book "A brand-new MacBook: $1,149. An LED Cinema Display Monitor $899. Crashing a Mac OS X system with only 11 lines of code: priceless". As the actual code that he used had three blank lines in it and several of the other lines in his code would often be combined into one line by those using alternative formatting I'd have called that six lines of code or possibly even five lines of code rather than 11.
3 internautes sur 3 ont trouvé ce commentaire utile 
Bug Hunting Showcased in most Spectacular Way 22 décembre 2011
Par Nagareshwar Talekar - Publié sur Amazon.com
Format: Broché
Once upon a time there were bounty hunters running in the wild to nab those `Most Wanted' criminals and walk away with big bucks. Now we have bug hunters running wild in their computer world not only to put their name on wall of fame but also to reap those rich rewards.

Here in this latest book "Bug Hunter's Diary" we have similar story of another great and inspiring bug hunter, Tobias Klein.

This book gives valuable insights on different techniques of bug hunting and exploiting them successfully. Each of the chapters in this book conforms to the each of the vulnerability discovered by author and written in his own words and style.

Before you proceed to reading, it is good idea to get some basic knowledge on driver concepts including its life cycle, IRP, IOCTL and debugging. As three of eight chapters here deal with driver bugs, this prep will help you to feel at home later on.

If you are new to vulnerability research, I suggest you to start with Appendix A which refreshes concept of stack overflow with practical example, NULL pointer dereferences, type conversion, GOT exploitation techniques which are essential to understand main chapters. Appendix B describes debugging tools along with commands for Solaris(mdb), Linux (gdb), Windows (windbg) and shows how to setup VMware for Kernel Debugging. Final Appendix talks about exploit mitigation techniques such as ASLR, GS, NX, DEP and finishes with detailed description on RELRO for ELF (Linux).

Though fuzzing is most common method used for bug hunting these days, author has used it only in final chapter and rest of the bugs were based on manual & his ingenious approach, that's what separates men from boys.

In chap 2, author talks about the first victim, VLC media player. He starts with traversing the source code, listing all demuxers dealing with different video formats, traces through the input data and finally finds Stack Overflow bug in TiVo demuxer code. Then he goes onto show how he manipulated sample Tivo video file to successfully exploit it.

In chap 3, author switches to one of his exceptional exploitation of NULL pointer dereference vulnerability in a network driver of Solaris Kernel. With source code it may be easy to find this bug but successfull exploitation of this bug was just amazing where author mapped the Zero/NULL page and then passed the controlled attack vectors through IOCTL to gain the root. Notable thing here is that vendor took more than year to patch the bug and author has to just wait in vain but do nothing. In fact real bounty hunting stories are not as sweet as they are shown on the screen.

Next chapter deals with tricky Type Conversion vulnerability in FFmpeg multimedia library (Linux). This is popular library used by Google Chrome, VLC Media Player, MPlayer etc. Here he finds bug beautiful bug in one of the demuxer code, (4xm.c file) dealing with 4X movie format. Conversion from user-controlled unsigned int media file to signed int caused the serious issue which author was able to exploit successfully to trigger remote code execution. Another job well done.

In chap 5, author shows us another interesting vulnerability in Cisco's WebEx ActiveX control for Internet Explorer [Windows]. Being researcher, he started with reversing this Activex control to find trivial string buffer overflow vulnerability. Then he realized that he could have done with by simply fuzzing. However it is interesting to see how author uses the tools like COMRaider, WinDbg, IDAPro in tandem to discover and exploit it.

Chap 6 talks about one of the stunning bug in kernel driver of Avast Antivirus software running in dark world of Windows. He starts with looking at Driver's poor security settings that allowed anyone to send IOCTL. Then he gets into reversing IOCTL handler code in the driver using IDA and finally finds bug in one of memcpy() calls deep down the rabbit hole. Admirable thing here is that Avast has fixed this kernel driver bug in just 10 days. Not all bounty hunting stories are as bad as depicted on the screen ;)

In chap 7, author turns to MAC, finding bug in XNU Kernel driver. He downloads the kernel code, traverses through IOCTL handlers and finally discovers another Type Conversion bug leading to blue screen. Then author goes through another challenging cycle of debugging through his cross wired Linux system to script a successful exploit to pwn his MAC.

Final chapter deals with interesting vulnerability in iPhone. Author finally uses his own custom fuzzer, simple yet smart, to discover bug audio ringtone processing code. Though iPhone flunked many times during fuzzing, he continued through the tedious process and discovers this as well as similar bugs in mediaserverd deamon. Next he gets into debugging his iPhone through GDB on Linux, finally stopping at successful exploitation. Bounty hunters does not seem to stop anywhere until they nail the man they are after!


* Be warned - Highly technical and Toxic, Keep a can of beer beside you :)
* For better digestion, read one chapter at a time with clear and cool head
* Deep exposure to vuln discovery and exploitation techniques on Windows, Linux, Solaris, Mac & iPhone
* Detailed technical steps with screenshots and code snippets
* No exploit code due to strict German laws but author has published videos
* Author does not preach but shows you what amazing things one can do with right skills and great patience

When you finish this book, it will not be hard for you to acknowledge Tobias Klein as one of those rare, genius and versatile bug hunter. It takes a lot to master those traits, not just knowing about it but to get to the r00t, you can't express it in words.

"This in not just a book that will teach you the Art of Bug Hunting in most spectacular way but an great inspiration to all those wanna be Bug Hunters !"

Disclaimer: I have received this book from the publisher for special review. However the review remains genuine and unbiased.
3 internautes sur 3 ont trouvé ce commentaire utile 
Great book for the hardcore 17 novembre 2011
Par James O'Gorman - Publié sur Amazon.com
Format: Broché
I have followed Tobias's work for some time via his blog, and when I found out that this book was coming out I was pretty excited. Upon getting the chance to read it, I was not let down at all. Anytime anyone works in exploits on a regular basis, something they are bound to hear quite often is "how are these exploits found?". This book is a wonderful guide through a number of different options for identification of initial bugs, and in some cases what the publisher did to correct the issue.

I was surprised too with the amount of variety of different types of bugs and platforms that were covered as well. But, its not a brief tour with no depth at all, as each issue is ran to ground in a very detailed manner. This is great, as the book can serve two different functions. First, a great introduction to vulnerability identification for those curious about the topic and thinking this might be a great way to spend their time. And second, for those already in the field it is a great source of study material to reproduce the same work in a guided manner.

Its not a book for lightweights however, be sure to use the look inside function and get an idea of what you are dealing with. Knowledge of how a debugger works, and at least some idea of how to read asm should be considered a bare minium for getting into the title. This is really good from my POV, as there is nothing more annoying then a book covering a highly technical topic that still tries to hold everyones hand all the way through. This book covers its core topic really well, and leaves the prerequisites to be your responsibility.

There are a lot of nice production details in the book as well, like for instance the graphics that show memory layout. Its a small thing, but the sort of hand drawn style is really nice and those sort of details make the book that much more pleasant to read.

The appendixes are really done well too, with lots of little details and tricks that come in useful a lot. Don't over look them if you pick the title up.

I have recommended this book to a lot of people in person, and its great that a title like this with such a niche topic can get published. I know a lot of people that are always hungry for this sort of information, and its really cool to see it coming from a main stream source.
Ces commentaires ont-ils été utiles ? Dites-le-nous


Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?