on
30-Oct-2022
18:00
- edited on
27-Apr-2023
15:04
by
LiefZimmerman
In this OWASP Automated Threat Article we'll be highlighting OAT-013 Sniping with some basic threat information as well as a recorded demo to dive into the concepts deeper. In our demo we'll explain how sniping works to leave insufficient time for another user to bid on a product. We'll wrap it up by highlighting F5 Bot Defense to show how we solve this problem for our customers.
Sniping
Last minute bid or offer for goods or services.
Sectors Targeted | Parties Affected | Data Commonly Misused | Other Names and Examples | Possible Symptoms |
Entertainment | Few Individual Users | Other Financial Data | Auction Sniping |
Elevated basket abandonment |
Financial | Application Owner | Other Business Data | Bid Sniper |
Reduced average basket price |
Retail | Third Parties | Last Minute Bet |
Higher proportion of failed payment authorisations |
|
Disproportionate use of the payment step | ||||
Increased chargebacks | ||||
Multiple failed payment authorizations from the same user and/or IP address and/or User Agent and/or session and/or deviceID/fingerprint |
In this presentation we will be discussing how attackers leverage automation to execute sniping bids against the application to win last second bids. We'll then show you how to quickly protect you application with F5 Distributed Cloud Bot Defense.
Sniping remains a very common practice to win auctions where bidding is based on timing and last minute execution of that bid. It is very preventable if appropriate anti-automation controls are put into place.