tree 336aa943ef0b8b6de70dfeb02183290092139a59
parent 7278700c32ec763b56efa1f5995c120c8af0140e
author David Navarro <dnav@users.noreply.github.com> 1648476243 +0200
committer GitHub <noreply@github.com> 1648476243 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJiQcBTCRBK7hj4Ov3rIwAAyBkIAI/YLk7ez4AEAIcC7ZTX96FT
 cXbvKP6iFYVWeal57riNH2DcyVj/8aEZt664Zu6ervuETEGDTRVj8uPGb/Kg+s8g
 VA6pxmNV/n9gFA5q/sfIm5AwAa1GMhEmQ1rNtwAXCEFAZx/7dw+qWtcXIVMCeyI8
 f6hQRKCMYj28cjR1azYRR0SuLyL7znhSEuIbGElkLdW0RkVOmNnZKV447u12gb7v
 f3rytMzNtNuccFolz1/XsDoz2rphwR2cnEXS+Lt4Sru+V+cyxiCQgMDOaXAeY2kC
 NRMg6OYyBc6eciXqER4Qnf4JL4yE2Oz5VGpItqircqhbdXrp/XqqpoUV4JV4RqA=
 =DcDZ
 -----END PGP SIGNATURE-----
 

Handle zero-length chunks in indefinite-length strings

Previously this would generate a QCBOR_ERR_STRING_ALLOCATE error.  There is no security issue or attack vector here. QCBOR just errored out on a zero-length string chunk when it should not have.  Zero-length string chunks are explicitly allowed in RFC 8949

Thanks David for the catch and the fix!


* Fix decoding of an indefinite-length string with a zero-length first chunk. (#134)

Signed-off-by: David Navarro <david.navarro@ioterop.com>

* Add an unit test for #134.

Signed-off-by: David Navarro <david.navarro@ioterop.com>

Co-authored-by: David Navarro <david.navarro@ioterop.com>