Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, SQL injection attacks can use an unescaped ORDER BY clause as a vector. There's an explanation of how this can be exploited and how to avoid this problem here:</p> <p><a href="http://josephkeeler.com/2009/05/php-security-sql-injection-in-order-by/" rel="noreferrer">http://josephkeeler.com/2009/05/php-security-sql-injection-in-order-by/</a></p> <p>That blog post recommends using a white list to validate the ORDER BY parameter against, which is almost certainly the safest approach.</p> <hr> <p>To respond to the update, even if the clause is complex, you can still write a routine that validates it against a whitelist, for example:</p> <pre><code>function validate_order_by($order_by_parameter) { $columns = array('first_name', 'last_name', 'zip', 'created_at'); $parts = preg_split("/[\s,]+/", $order_by_parameter); foreach ($parts as $part) { $subparts = preg_split("/\s+/", $part); if (count($subparts) &lt; 0 || count($subparts) &gt; 2) { // Too many or too few parts. return false; } if (!in_array($subparts[0], $columns)) { // Column name is invalid. return false; } if (count($subparts) == 2 &amp;&amp; !in_array(strtoupper($subparts[1]), array('ASC', 'DESC')) { // ASC or DESC is invalid return false; } } return true; } </code></pre> <p>Even if the ORDER BY clause is complex, it's still made only out of values you supply (assuming you're not letting users edit it by hand). You can still validate using a white list.</p> <p>I should also add that I normally don't like to expose my database structure in URLs or other places in the UI and will often alias the stuff in the parameters in the URLs and map it to the real values using a hash. </p>
    singulars
    1. This table or related slice is empty.
    1. POIs there anything that can be put after the "ORDER BY" clause that can pose a security risk?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRafe
    1. USRafe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there anything that can be put after the "ORDER BY" clause that can pose a security risk?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CORafe, I think it would be very valuable to show/explain the whitelist example here. It allows the OP to incorporate his method more defensively, and (looks like) a great technique in general.
      singulars
      1. PO
      1. USNic
    2. COWhite-listing isn't trivial to implement when the variable is not a single column name, but an actual chunk of SQL (see updated Q).
      singulars
      1. PO
      1. USmpen
    3. COYou don't have to make the $_GET parameter correspond to column names, you could use the parameter in a `case` statement, and based on the parameter value, conditionally add any column(s) or expression(s) you want.
      singulars
      1. PO
      1. USBill Karwin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload