How do you protect your server from SQL injection?

How do you protect your server from SQL injection?
Do we even need to worry about it when almost all major languages provide some form of parameter binding?

Attached: 1634086050478.png (409x475, 265.99K)

Other urls found in this thread:

e-hentai.org/g/2266816/a616acd965/
twitter.com/NSFWRedditGif

are those the Arch panties?

sauce and I'll answer your question

they're rice bowl panties

You use popular ORMs. You aren't better at preventing injection attacks than these libraries so don't even waste your time trying

What a stupid fucking question. Sanitize inputs or use an ORM that sanitizes for you (most of them do). Would've taken 5 seconds to find that on Jewgle

>SQL injection
Is it 2007 again?

You don't need a fucking ORM to sanitize your inputs. Just use prepared statements like a sane person if you have no need for an ORM.

I've gotten into arguments at work with devs who are too lazy to use prepared statements because something is "probably not injectable by a user" it still happens when you have devs more interested in closing a ticket so they don't get fired vs actually implementing shit right the first time

That's exactly the kind of mentality which results in data breaches, losing money and getting fired.
You should find a way to teach those retards that one should never trust an user input string unless it is sanitized.

by not using shitty langs

Either use a rock solid ORM (RoR's Active Record for example isn't good at preventing SQL injections). Or write your own prepaired statements.

>You don't need a fucking ORM to sanitize your inputs
What else do you use retard?
>inb4 prepared statements
not as secure

>How do you protect your server from SQL injection?
You simply need to educate your SQL developers about it.
Considering the topic of SQL injection could be explained in five minutes, it shouldn't be too difficult.

works as designed. systems are not designed for security but for deniability. even if you could do things right the first time, policy will be crafted with expectations that make it impossible in order to keep employees on a treadmill of barely meeting some arbitrary quota. when someone gets fired this way it's not even their fault even if they where incompetent, the game was rigged from the start.

Attached: unknown_8_11.png (1125x1382, 2.82M)

sauce?

>not as secure
Elaborate.

Can someone genuinely answer why the fuck that in the year of our lord 2022 SQL is still used in industry when it has SO many security and design flaws?

Unsanitized input is not a problem unique to SQL.

Where else is it this big of a problem?

XSS, the entire log4j rce, just google unsanitized input exploit

Fucking coomers
e-hentai.org/g/2266816/a616acd965/