HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-217 days agoSQL Injectionlemmy.mlimagemessage-square18fedilinkarrow-up1269arrow-down15file-textcross-posted to: [email protected][email protected]
arrow-up1264arrow-down1imageSQL Injectionlemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-217 days agomessage-square18fedilinkfile-textcross-posted to: [email protected][email protected]
minus-squareMadhuGururajan@programming.devlinkfedilinkEnglisharrow-up1·4 days agoNo the interviewer is personification of the naive backend that checks only that a specific row is present in the DB, or that’s how I read it.
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up1·4 days agoSo I guess the interview is handled by a non-vulnerable intermediate process, which adds the hire to the the main table of employees when at some point in a successful interview, and then calls a notification process that just searches it?
minus-squareMadhuGururajan@programming.devlinkfedilinkEnglisharrow-up2·4 days agoyeah something like “if new candidate in employee DB == hired”
No the interviewer is personification of the naive backend that checks only that a specific row is present in the DB, or that’s how I read it.
So I guess the interview is handled by a non-vulnerable intermediate process, which adds the hire to the the main table of employees when at some point in a successful interview, and then calls a notification process that just searches it?
yeah something like “if new candidate in employee DB == hired”