禅道 12.3.3 版本发布，主要修复Bug

请问版本11.6.1也存在sql注入漏洞吗？请问在不升级的情况下，这个sql注入漏洞怎么解决呢？是在module\api\control和model中吗，我下载最新的12.3.3代码发现这两个文件并没有变化

添加项目 添加产品 直接报404 其他正常

centos8+mysql8环境安装运行mariadb失败，请问禅道必须依赖mariadb吗？

一键安装包，命令 /opt/zbox/zbox -ap 8013 -mp 3307
[root@server-pc opt]# /opt/zbox/zbox -ap 8013 -mp 3307
[root@server-pc opt]# /opt/zbox/zbox start
Start Apache fail. You can see the log /opt/zbox/logs/apache_error.log
Start Mysql fail. You can see the log /opt/zbox/logs/mysql_error.log

报错信息，只有myql
2020-07-15 15:40:08 0 [Note] InnoDB: Using Linux native AIO
2020-07-15 15:40:08 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-07-15 15:40:08 0 [Note] InnoDB: Uses event mutexes
2020-07-15 15:40:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-15 15:40:08 0 [Note] InnoDB: Number of pools: 1
2020-07-15 15:40:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-07-15 15:40:08 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-07-15 15:40:08 0 [Note] InnoDB: Completed initialization of buffer pool
2020-07-15 15:40:08 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-07-15 15:40:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1603959
200715 15:40:08 [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 https://mariadb.com/kb/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.3.13-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 137278 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x30000
/opt/zbox/run/mysql/mysqld(my_print_stacktrace+0x29)[0x5581a98f7279]
/opt/zbox/run/mysql/mysqld(handle_fatal_signal+0x57d)[0x5581a944717d]
/opt/zbox/run/lib/libpthread.so.0(+0x12890)[0x7f64fafe1890]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0xcac8)[0x7f64fcc0eac8]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x150bd)[0x7f64fcc170bd]
/opt/zbox/run/lib/libc.so.6(_dl_catch_exception+0x6f)[0x7f64fa3b92df]
/opt/zbox/run/lib/ld-linux-x86-64.so.2(+0x147ca)[0x7f64fcc167ca]
/opt/zbox/run/lib/libc.so.6(+0x1663ad)[0x7f64fa3b83ad]
/opt/zbox/run/lib/libc.so.6(_dl_catch_exception+0x6f)[0x7f64fa3b92df]
/opt/zbox/run/lib/libc.so.6(_dl_catch_error+0x2f)[0x7f64fa3b936f]
/opt/zbox/run/lib/libc.so.6(__libc_dlopen_mode+0x89)[0x7f64fa3b84d9]
/opt/zbox/run/lib/libpthread.so.0(+0x12deb)[0x7f64fafe1deb]
/opt/zbox/run/lib/libpthread.so.0(+0x12fd4)[0x7f64fafe1fd4]
/opt/zbox/run/lib/libpthread.so.0(__pthread_unwind+0x40)[0x7f64fafdff10]
/opt/zbox/run/lib/libpthread.so.0(+0x8ae5)[0x7f64fafd7ae5]
/opt/zbox/run/mysql/mysqld(+0x490ad5)[0x5581a91bfad5]
/opt/zbox/run/mysql/mysqld(+0x8d4fd6)[0x5581a9603fd6]
/opt/zbox/run/lib/libpthread.so.0(+0x76db)[0x7f64fafd66db]
/opt/zbox/run/lib/libc.so.6(clone+0x3f)[0x7f64fa37388f]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

ZenTaoPMS.12.3.3.win64.exe 包里头内容有错！

E:\xampp\zentao\config\my.php 里头，password 被填成 3306 了，导致禅道代码根本连不上本机数据库，正确的密码是 123456 。