@youTellMe to Programmer HumorEnglish • 4 days agoEveryday we stray further from industry standardsimagemessage-square24arrow-up1187arrow-down11
arrow-up1186arrow-down1imageEveryday we stray further from industry standards@youTellMe to Programmer HumorEnglish • 4 days agomessage-square24
minus-square@[email protected]linkfedilinkEnglish15•edit-23 days agoGET /api/database?query=SELECT+++name+++FROM+++users+++WHERE+++id=42 I’ve seen that exact type of endpoint, hitting databases in production. 🔥
minus-square@surewhynotlemlinkEnglish1•3 days agoIf that’s a pass through, that’s bad. If that’s used for authentication, authorization, credential limiting, or rate limiting, then sure.
minus-square@[email protected]linkfedilinkEnglish3•3 days agoThere is no context in this world validating this level of unsanitized SQL. Even for internal use this is bad, since it bypasses the auth of server and dbms.
GET /api/database?query=SELECT+++name+++FROM+++users+++WHERE+++id=42I’ve seen that exact type of endpoint, hitting databases in production. 🔥
If that’s a pass through, that’s bad.
If that’s used for authentication, authorization, credential limiting, or rate limiting, then sure.
There is no context in this world validating this level of unsanitized SQL. Even for internal use this is bad, since it bypasses the auth of server and dbms.
That is a very good point.