1. 14 Dec, 2016 2 commits
  2. 09 Dec, 2016 1 commit
  3. 01 Dec, 2016 1 commit
    • SachinSetiya's avatar
      MDEV-11016 wsrep_node_is_ready() check is too strict · 72fd15f7
      SachinSetiya authored
            Problem:-
            The condition that checks for node readiness is too strict as it does
            not allow SELECTs even if these selects do not access any tables.
            For example,if we run
                 SELECT 1;
            OR
                 SELECT @@max_allowed_packet;
            Solution:-
            We need not to report this error when all_tables(lex->query_tables)
            is NULL:
      72fd15f7
  4. 09 Nov, 2016 1 commit
  5. 17 Oct, 2016 1 commit
  6. 14 Oct, 2016 2 commits
  7. 13 Oct, 2016 6 commits
  8. 29 Sep, 2016 1 commit
  9. 28 Sep, 2016 3 commits
  10. 27 Sep, 2016 1 commit
  11. 26 Sep, 2016 5 commits
  12. 24 Sep, 2016 1 commit
  13. 22 Sep, 2016 1 commit
  14. 19 Sep, 2016 1 commit
  15. 13 Sep, 2016 1 commit
  16. 12 Sep, 2016 4 commits
  17. 11 Sep, 2016 1 commit
  18. 02 Sep, 2016 1 commit
  19. 26 Aug, 2016 1 commit
  20. 25 Aug, 2016 4 commits
    • Sivert Sorumgard's avatar
      Bug#24388753: PRIVILEGE ESCALATION USING MYSQLD_SAFE · 48bd8b16
      Sivert Sorumgard authored
      [This is the 5.5/5.6 version of the bugfix].
      
      The problem was that it was possible to write log files ending
      in .ini/.cnf that later could be parsed as an options file.
      This made it possible for users to specify startup options
      without the permissions to do so.
      
      This patch fixes the problem by disallowing general query log
      and slow query log to be written to files ending in .ini and .cnf.
      48bd8b16
    • Jon Olav Hauglid's avatar
      Bug#24388746: PRIVILEGE ESCALATION AND RACE CONDITION USING CREATE TABLE · 4e547386
      Jon Olav Hauglid authored
      During REPAIR TABLE of a MyISAM table, a temporary data file (.TMD)
      is created. When repair finishes, this file is renamed to the original
      .MYD file. The problem was that during this rename, we copied the
      stats from the old file to the new file with chmod/chown. If a user
      managed to replace the temporary file before chmod/chown was executed,
      it was possible to get an arbitrary file with the privileges of the
      mysql user.
      
      This patch fixes the problem by not copying stats from the old
      file to the new file. This is not needed as the new file was
      created with the correct stats. This fix only changes server
      behavior - external utilities such as myisamchk still does
      chmod/chown.
      
      No test case provided since the problem involves synchronization
      with file system operations.
      4e547386
    • Terje Rosten's avatar
      Bug#24464380 PRIVILEGE ESCALATION USING MYSQLD_SAFE · 684a165f
      Terje Rosten authored
      Argument to malloc-lib must be included in restricted list of
      directories, symlink guards added, and mysqld and mysqld-version
      options restricted to command line only. Don't redirect errors to
      stderr.
      684a165f
    • Monty's avatar
      DEV-10595 MariaDB daemon leaks memory with specific query · ee97274c
      Monty authored
      The issue was that in some extreme cases when doing GROUP BY,
      buffers for temporary blobs where not properly cleared.
      ee97274c
  21. 19 Aug, 2016 1 commit