Memory leak in v3 hsdesc parsing with empty encrypted data.
When we get a v3 hsdesc where the decrypted part starts with a NUL byte, then decrypt_desc_layer will return 0, since the length of the output is 0. But "0" can also mean that there's an error in the decryption.
Found with OSS-fuzz.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information