Run this HTTP https://nanomq.io/docs/en/latest/api/v4.html#update-configuration-file  request and you will see the NanoMQ server crash


 INFO  /home/runner/work/nanomq/nanomq/nanomq/rest_api.c:2591 update_config: Writting new config to (null)


 ERROR /home/runner/work/nanomq/nanomq/nanomq/apps/broker.c:104 sig_handler: signal signumber: 11 received!


update config_update using Http server api/v4  crash server  
This is a GitHub Issue
repo:nanomq
owner:emqx
Title : update config_update using Http server api/v4  crash server  
Issue date:

--- start body ---
Run this HTTP https://nanomq.io/docs/en/latest/api/v4.html#update-configuration-file  request and you will see the NanoMQ server crash


 INFO  /home/runner/work/nanomq/nanomq/nanomq/rest_api.c:2591 update_config: Writting new config to (null)


 ERROR /home/runner/work/nanomq/nanomq/nanomq/apps/broker.c:104 sig_handler: signal signumber: 11 received!


--- end body ---

The issue indicates a potential vulnerability in the NanoMQ server where an HTTP request to update the configuration can lead to a crash. The log shows that the server attempts to write a new configuration to a null pointer, which results in a segmentation fault (signal number 11). This could be exploited to cause a Denial of Service (DoS) by sending crafted requests to the server.