Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Indeed, the prod/test example is neat. I'm still less impressed than other usual DML injection. Do you have any other idea how to read or alter data in the tables through that single injection (without relying on other queries from the normal process flow being fired on the "wrong" database)? Commented Aug 1, 2019 at 15:55
  • Certainly it’s not as generically useful as an exploit that lets you break out of the existing SQL. If I was attacking the system, I’d be trying to find a way to escape the restrictions preventing that. Regardless, it probably should be fixed now, even if there isn’t a visible exploit. Consider that in the future someone else may migrate the database to a prod/test type of configuration, at which point it would become vulnerable. Or maybe they migrate it to Postgres, which could be vulnerable. Too many possibilities for the future. Commented Aug 1, 2019 at 20:54