Sumeru Cyber Security
  • Sumeru Cyber Security
  • Workarounds for prevalent vulnerabilities
    • Version Disclosure
    • Host Header Attack
    • HttpOnly and Secure Flag
    • Security Headers
    • Clickjacking
    • Weak Password
    • Username Enumeration
    • jQuery Outdated
    • Cross-Origin Resource Sharing
    • AWS S3 Bucket Misconfiguration
    • Directory Listing
    • Laravel Debug Enabled
    • Autocomplete and Remember Password Enabled
    • Brute Force Attack
    • Cross Site Request Forgery
    • SQL Injection
    • PhpMyAdmin page Available Publicly
    • Implementation of BASIC Authentication
    • Cache Browsing
    • Insecure Direct Object Reference
    • Active mixed content over https
    • Improper forgot password implementation
    • ASP.NET Debug Enabled
    • Sensitive Data Sent in GET Request
    • Weak CAPTCHA Implementation
    • Csv Injection
    • Cross Site Scripting
    • Web Server Robot.txt Information Disclosure
    • SSL Related Issues
    • Local File Inclusion
    • Weak CAPTCHA Implementation
    • Automated Form Submission
    • Php.ini File Available Publicly
    • ITLP
    • Internal Path Disclosure
    • Insecure Direct Object Reference
    • Access Token Not Expiring After Logout
  • OWASP A09-Security Logging and Monitoring Failures
  • OWASP API09-Improper Inventory Management v1.0
Powered by GitBook
On this page
  • Introduction
  • How to Test
  • How to Fix
  • Captcha Implementation:
  • Throttling:
  • References:

Was this helpful?

  1. Workarounds for prevalent vulnerabilities

Brute Force Attack

PreviousAutocomplete and Remember Password EnabledNextCross Site Request Forgery

Last updated 5 years ago

Was this helpful?

Introduction

A Brute Force Attack is the simplest method to gain access to a site or server (or anything that is password protected). It tries various combinations of usernames and passwords again and again until it gets in.

How to Test

Using Burpsuite, capture the login request.

Select the payload type and add the payloads contains possible combination of letters, numbers, and symbols to the list.

With the payloads it tries to login to the site until it found the right one.

Here we can find, for the correct password the length and status of the response changes.

How to Fix

Captcha Implementation:

A CAPTCHA is normally intended to ensure that 'user' input is from a real person. It could help to prevent automated attacks against a website login mechanism.

<script src='https://www.google.com/recaptcha/api.js'></script>

Throttling:

The Throttler class provides a very simple way to limit an activity to be performed to a certain number of attempts within a set period of time. This is most often used for performing rate limiting on API’s, or restricting the number of attempts a user can make against a form to help prevent brute force attacks. The class itself can be used for anything that you need to throttle based on actions within a set time interval.

$throttler = \Config\Services::throttler(); 
$throttler->check($name, 60, MINUTE);

References:

https://owasp.org/www-community/controls/Blocking_Brute_Force_Attacks
https://developers.google.com/recaptcha/
https://webdesign.tutsplus.com/tutorials/how-to-integrate-no-captcha
recaptcha-in-your-website--cms-23024
https://codeigniter4.github.io/userguide/libraries/throttler.html