Update documentation related to SQL injection with raw queries#5735
Conversation
|
@joshbouncesecurity is attempting to deploy a commit to the Prisma Team on Vercel. A member of the Team first needs to authorize it. |
jharrell
left a comment
There was a problem hiding this comment.
Thank you very much @joshbouncesecurity !
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
see internal Slack discussion: https://prisma-company.slack.com/archives/C058VM009HT/p1710493203426249
jharrell
left a comment
There was a problem hiding this comment.
Few notes from our internal review. Thank you again @joshbouncesecurity
Co-authored-by: Jon Harrell <4829245+jharrell@users.noreply.github.com>
Co-authored-by: Jan Piotrowski <piotrowski+github@gmail.com>
|
Hi @janpio I think I handled all your comments except this one which I think is better not changed. You can see the specific updates here: |
Co-authored-by: Jan Piotrowski <piotrowski+github@gmail.com>
|
Thank you again for all your help @joshbouncesecurity ! We really appreciate you working with us and a special thanks for your contribution 🙂 |
|
You're welcome, I always like to see more detailed security documentation :) |
Describe this PR
See discussion here;
https://discord.com/channels/937751382725886062/1218200207884288071
Basically, the docs make it seem like
queryRawandexecuteRaware safe from SQL injection when it fact is possible to use them unsafely as well.I have prepared an update to the documentation to reflect this.
Changes
queryRawandexecuteRaware used safely in a simple case.queryRawandexecuteRawcan also be used unsafely.queryRawandexecuteRawcan be used safely in more complicated cases as well.What issue does this fix?
N/A
Any other relevant information
I deliberately tried to make all examples compatible with the Prisma playground so you can verify them.