QA Engineer walks into a bar.
Orders a beer. Orders 0 beers. Orders 999999999 beers. Orders a lizard. Orders -1 beers. Orders a sfdeljknesv.
Hug your QA engineers, they save you from eternal embarrassment.
Orders a beer. Orders 0 beers. Orders 999999999 beers. Orders a lizard. Orders -1 beers. Orders a sfdeljknesv.
Hug your QA engineers, they save you from eternal embarrassment.
Beer delivered, but at the center of the bar, not to the customer.
> Orders 0 beers.
> Orders 999999999 beers.
Bar room fills up with beer, drowning everyone.
> Orders a lizard.
Bartender yells gibberish at customer.
> Orders -1 beers.
Keg explodes in taproom.
> Orders a sfdeljknesv.
Bartender complements customer on their fine taste in Hungarian beer.
If you are attacking with the intent of stealing information it would likely better to use the database injection as the foundation for multiple pivots into other systems that would presumably have more valuable stuff than a list of people who bought a beer and or their credit card numbers.
The bar gets flooded by the contents of hundreds of broken bottles.