youTellMe@lemmy.world to Programmer Humor@lemmy.worldEnglish · 2 months agoEveryday we stray further from industry standardslemmy.worldimagemessage-square24fedilinkarrow-up1187arrow-down11
arrow-up1186arrow-down1imageEveryday we stray further from industry standardslemmy.worldyouTellMe@lemmy.world to Programmer Humor@lemmy.worldEnglish · 2 months agomessage-square24fedilink
minus-squaresebsch@discuss.tchncs.delinkfedilinkEnglisharrow-up15·edit-22 months agoGET /api/database?query=SELECT+++name+++FROM+++users+++WHERE+++id=42 I’ve seen that exact type of endpoint, hitting databases in production. 🔥
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoIf that’s a pass through, that’s bad. If that’s used for authentication, authorization, credential limiting, or rate limiting, then sure.
minus-squaresebsch@discuss.tchncs.delinkfedilinkEnglisharrow-up3·2 months 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.
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoThat is a very good point.
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.