Book Image

Mastering Modern Web Penetration Testing

By : Prakhar Prasad, Rafay Baloch
Book Image

Mastering Modern Web Penetration Testing

By: Prakhar Prasad, Rafay Baloch

Overview of this book

Web penetration testing is a growing, fast-moving, and absolutely critical field in information security. This book executes modern web application attacks and utilises cutting-edge hacking techniques with an enhanced knowledge of web application security. We will cover web hacking techniques so you can explore the attack vectors during penetration tests. The book encompasses the latest technologies such as OAuth 2.0, Web API testing methodologies and XML vectors used by hackers. Some lesser discussed attack vectors such as RPO (relative path overwrite), DOM clobbering, PHP Object Injection and etc. has been covered in this book. We'll explain various old school techniques in depth such as XSS, CSRF, SQL Injection through the ever-dependable SQLMap and reconnaissance. Websites nowadays provide APIs to allow integration with third party applications, thereby exposing a lot of attack surface, we cover testing of these APIs using real-life examples. This pragmatic guide will be a great benefit and will help you prepare fully secure applications.
Table of Contents (18 chapters)
Mastering Modern Web Penetration Testing
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Introducing the OAuth 2.0 model


OAuth 2.0 basically allows a third party website to access a limited or selective set of user information on a particular website. There are different kinds of authorization flows used in OAuth 2.0. The main reason that OAuth exists is the fact that in the classic authentication model, the user's account credentials are generally shared with the third party website, which results in several problems; these are documented well in the OAuth 2.0 RFC 6749.

  • The third party can save the credentials in plain-text

  • The third party gets a large amount of access to users' data, typically full account access

  • There is no proper method to revoke access given to a third party without revoking all other third parties because the credentials are common to all third parties

If any third party is compromised, it will result in compromise of the credentials of the end user. Now, let's get started with OAuth 2.0.

OAuth 2.0 roles

There are primarily four kinds of roles present in OAuth...