Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10361

auth_pam + RSA SecurID PAM module + SQLyog causes server crash

Details

    Description

      A user saw the following server crash in auth_pam when connecting to MariaDB server using SQLyog, which is linked with MariaDB Connector/C:

      160711 14:39:55 [ERROR] mysqld got signal 11 ;
      		 
      This could be because you hit a bug. It is also possible that this binary
      		 
      or one of the libraries it was linked against is corrupt, improperly built,
      		 
      or misconfigured. This error can also be caused by malfunctioning hardware.
      		 
       
      		 
      To report this bug, see http://kb.askmonty.org/en/reporting-bugs
      		 
       
      		 
      We will try our best to scrape up some info that will hopefully help
      		 
      diagnose the problem, but since we have already crashed,
      		 
      something is definitely wrong and this may fail.
      		 
       
      		 
      Server version: 10.1.10-MariaDB-log
      		 
      key_buffer_size=134217728
      		 
      read_buffer_size=131072
      		 
      max_used_connections=6
      		 
      max_threads=502
      		 
      thread_count=5
      		 
      It is possible that mysqld could use up to
      		 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1233659 K bytes of memory
      		 
      Hope that's ok; if not, decrease some variables in the equation.
      		 
       
      		 
      Thread pointer: 0x0x7f6580f3d008
      		 
      Attempting backtrace. You can use the following information to find out
      		 
      where mysqld died. If you see no messages after this, something went
      		 
      terribly wrong...
      		 
      stack_bottom = 0x7f72ba5f4d30 thread_stack 0x48000
      		 
      mysys/stacktrace.c:247(my_print_stacktrace)[0x7f72c0a7536e]
      		 
      sql/signal_handler.cc:160(handle_fatal_signal)[0x7f72c05a36ad]
      		 
      /lib64/libpthread.so.0(+0xf100)[0x7f72bfbc5100]
      		 
      /usr/lib64/security/pam_securid.so(+0x12d83)[0x7f72ba41fd83]
      		 
      /usr/lib64/security/pam_securid.so(+0x13f24)[0x7f72ba420f24]
      		 
      /usr/lib64/security/pam_securid.so(+0x15160)[0x7f72ba422160]
      		 
      /usr/lib64/security/pam_securid.so(pam_sm_authenticate+0x3bd)[0x7f72ba421e46]
      		 
      /lib64/libpam.so.0(+0x2f6a)[0x7f72b0aadf6a]
      		 
      /lib64/libpam.so.0(pam_authenticate+0x30)[0x7f72b0aad830]
      		 
      /usr/lib64/mysql/plugin/auth_pam.so(+0xf1e)[0x7f72b0cbaf1e]
      		 
      sql/sql_acl.cc:12263(do_auth_once)[0x7f72c03b8341]
      		 
      sql/sql_acl.cc:12374(acl_authenticate(THD*, unsigned int))[0x7f72c03daf5d]
      		 
      sql/sql_connect.cc:1024(check_connection)[0x7f72c04f08df]
      		 
      sql/sql_connect.cc:1092(login_connection(THD*))[0x7f72c04f2275]
      		 
      sql/sql_connect.cc:1270(thd_prepare_connection(THD*))[0x7f72c04f2be9]
      		 
      sql/sql_connect.cc:1340(do_handle_one_connection(THD*))[0x7f72c04f2db0]
      		 
      sql/sql_connect.cc:1263(handle_one_connection)[0x7f72c04f2fb0]
      		 
      /lib64/libpthread.so.0(+0x7dc5)[0x7f72bfbbddc5]
      		 
      /lib64/libc.so.6(clone+0x6d)[0x7f72bdfdf28d]
      		 
       
      		 
      Trying to get some variables.
      		 
      Some pointers may be invalid and cause the dump to abort.
      		 
      Query (0x0): is an invalid pointer
      		 
      Connection ID (thread ID): 19
      		 
      Status: NOT_KILLED
      		 
       
      		 
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=on,mrr_cost_based=on,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on

      RSA SecurID implements multi-factor authentication. The crash seems to occur when SQLyog attempts to automatically reconnect with the user's previously-entered PIN, which was only intended for 1 use.

      This might indicate a bug in the RSA SecurID PAM module. This one looks similar:

      https://www.redhat.com/archives/pam-list/2015-April/msg00003.html

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-15473 Isolate/sandbox PAM modules, so that they can't crash the server

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 12 older comments
            GeoffMontee Geoff Montee (Inactive) added a comment -

            RSA was not very helpful:

            Unfortunately, We do not support SQLyog application and it is not in our scope. In RHEL, we do support SSH, Telnet, SU, Login, rlogin, ftp, sudo and gdm. I would request you to reach out to RHEL Team or SQLyog team to check about this.

            GeoffMontee Geoff Montee (Inactive) added a comment - RSA was not very helpful: Unfortunately, We do not support SQLyog application and it is not in our scope. In RHEL, we do support SSH, Telnet, SU, Login, rlogin, ftp, sudo and gdm. I would request you to reach out to RHEL Team or SQLyog team to check about this.
            serg Sergei Golubchik added a comment -

            I've pushed a commit that adds debug output to pam plugin into bb-10.1-serg branch. When it'll build, you can find binaries at the usual location.

            serg Sergei Golubchik added a comment - I've pushed a commit that adds debug output to pam plugin into bb-10.1-serg branch. When it'll build, you can find binaries at the usual location.
            serg Sergei Golubchik added a comment -

            It turned out to be an issue in SQLyog, not Connector/C or MariaDB.

            serg Sergei Golubchik added a comment - It turned out to be an issue in SQLyog, not Connector/C or MariaDB.
            GeoffMontee Geoff Montee (Inactive) added a comment -

            The user who reported this issue says that SQLyog still causes MariaDB to crash, and that the problem goes away if SQLyog is built with MySQL's connector instead of MariaDB Connector/C. This appears to be a bug in MariaDB and/or MariaDB Connector/C.

            GeoffMontee Geoff Montee (Inactive) added a comment - The user who reported this issue says that SQLyog still causes MariaDB to crash, and that the problem goes away if SQLyog is built with MySQL's connector instead of MariaDB Connector/C. This appears to be a bug in MariaDB and/or MariaDB Connector/C.
            GeoffMontee Geoff Montee (Inactive) added a comment -

            I'm closing this, because this problem probably reflects a bug in pam_securid.so which would have to be fixed by RSA rather than MariaDB.

            GeoffMontee Geoff Montee (Inactive) added a comment - I'm closing this, because this problem probably reflects a bug in pam_securid.so which would have to be fixed by RSA rather than MariaDB.

            People

              georg Georg Richter
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.