Benjamin Valentin 66fe083d9b nanocoap: always write at least 1 byte in coap_block2_finish() ...

The CoAP block option gets written twice:
First a 'dummy' value is written by `coap_opt_add_block2()`, later this gets
overwritten by the real option value by coap_block2_finish().

The problem arises when the size of the option changes.
If the option ends up smaller than the dummy, we have garbage bytes after the
real option value, corrupting the packet.

To mitigate this, always write at least one option byte (which will be a 0 byte)
to ensure the dummy data is overwritten.

fixes #20686

2024-09-07 16:11:23 +02:00

..

cache.c

Merge pull request #20043 from bergzand/pr/nanocoap_cache_options

2024-02-13 15:23:59 +00:00

fileserver.c

nanocoap_fileserver: add support for size2 option

2024-05-22 20:16:25 +02:00

fs.c

nanocoap_fs: add nanoCoAP as VFS backend

2024-05-29 11:32:22 +02:00

Kconfig

*Kconfig*: Modify Kconfig to remove dep model

2024-03-27 10:28:12 +01:00

link_format.c

nanocoap_link_format: don't drop characters in fragmented entries

2024-05-07 22:45:37 +02:00

Makefile

sys/net/nanocoap: use submodules

2017-12-01 12:55:45 +01:00

Makefile.include

sys/net/nanocoap: ensure DTLS buffer is at least 200 bytes

2024-04-03 21:09:29 +02:00

nanocoap.c

nanocoap: always write at least 1 byte in coap_block2_finish()

2024-09-07 16:11:23 +02:00

sock.c

treewide: remove THREAD_CREATE_STACKTEST from thread creation

2024-07-29 11:45:58 +02:00

vfs.c

nanocoap: homogenize name of the module

2023-06-08 16:29:12 +02:00