Comment on #NULL!

• copacetic@discuss.tchncs.de ⁨1⁩ ⁨week⁩ ago

  If you use the SQLite C API like this

      char query[256];
      snprintf(query, sizeof(query),
               "SELECT * FROM users WHERE username = '%s'", username);
      int rc = sqlite3_exec(db, query, NULL, NULL, &err_msg);
  

  and someone enters Robert’; DROP Table Students;– as username, it deletes the table Students.

      const char *sql = "SELECT * FROM users WHERE username = ?";
      int rc = sqlite3_prepare_v2(db, sql, -1, &stmt, NULL);
      if (rc != SQLITE_OK) {
          fprintf(stderr, "Failed to prepare statement\n");
          return;
      }
      sqlite3_bind_text(stmt, 1, username, -1, SQLITE_STATIC);
  

  Using this “prepared statement” and “bind”, your code is secured against such SQL injection attacks.

  source
• LovableSidekick@lemmy.world ⁨1⁩ ⁨week⁩ ago

  You wouldn’t - what they’re describing is called “SQL injection” - a way to fool poorly written web server code (regardless of what language it’s writen in) into executing SQL code. The poorly written server code takes what’s entered in a form field on a web page and pastes it into a skeleton of a SQL statement - in this case the text in the input field is SQL that ends the intended statement, followed by a new statement that deletes a table. For this to even work, the SQL skeleton on the server would have to be structured in just the right way so the modified version with the pasted-in text still makes sense. For this reason, hackers attempting SQL injection usually have to do a lot of trial and error to get something to happen. The only way it can work at all is if the server software handling the web page sends SQL commands to a database server as text, as if they’re being typed in, and the server executes them. You can’t inject C in this way because unlike SQL, C code isn’t just executed, C programs have to be precompiled.

  source
• jaybone@lemmy.zip ⁨1⁩ ⁨week⁩ ago

  Many languages like C, Java, Python, etc allow you to construct SQL queries or SQL statements, where SQL is its own language used to communicate with a database, like Oracle or MySql, or Postgres or MSSQL. One way to do this is to construct a string in your language using whatever string functions, concatenation etc available in your language. The problem occurs because usually you want some kind of user input as one of the parameters in your sql query, in order to fetch the correct records the user is asking for. Like say a record ID or name. If you do not properly sanitize that ID or name which originally comes from some type of user input, then a malicious user could carefully craft an ID or name which includes their own SQL and other special characters, which will interfere with the query you intended to construct, and instead do something malicious. Like delete records or obtain records the user is not supposed to have access to.

  There are many ways to guard against this, and you should learn about this when you start working with SQL and databases. It’s called a SQL injection.

  There is another type of code injection which can occur if you are making exec() calls (or whatever your language uses) to run shell commands. Similar caution should be taken there.

  source

  • thesystemisdown@lemmy.world ⁨1⁩ ⁨week⁩ ago

    I know what I’m dealing with when I see a query that isn’t using a prepared statement.

    source

    • jaybone@lemmy.zip ⁨1⁩ ⁨week⁩ ago

      I mean a prepared statement is still created with a string.

      But you definitely want to be using bind parameters with your prepared statements. Not only for security but also potentially performance improvements.

      source
• vrek@programming.dev ⁨1⁩ ⁨week⁩ ago

  How do you sanitize your inputs or how do you exploit inputs which are not sanitized.

  source

  • akunohana@piefed.blahaj.zone ⁨1⁩ ⁨week⁩ ago

    Santize inputs.

    I’ll get back to you on exploits when I can write something that throws zero compilation errors. 😈

    source

    • vrek@programming.dev ⁨1⁩ ⁨week⁩ ago

      Couple big things are 1. Only accept reasonable characters, on a white list instead of rejecting bad characters based on a black list. This will mean you are less likely to forget to block /0 for example. 2. Understand how strings work and ensure both reading and writing to that string doesn’t extend beyond the end of memory allocated for the string. For example do you understand what the /0 would do to a string your program accepts?

      source

      • brbposting@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

        Is it easy for a good developer to allow new lines without any extra security risk exposure?

        Sometimes e.g. a government form will remove new lines, though perhaps sometime they intend to reduce length.

        source

        • -> View More Comments
      • akunohana@piefed.blahaj.zone ⁨1⁩ ⁨week⁩ ago

        Sic! Thanks! I’ll work on this this weekend! 😊

        source

        • -> View More Comments