-
CBOR (RFC 7049) is a binary data format inspired by JSON and MessagePack. CBOR is used in IETF Internet Standards such as COSE (RFC 8152) and CWT (RFC 8392 CBOR Web Token).
Please add a method to …
-
@g-k 🔥 this CBOR security issue is already public knowledge and affects a library used by go-cose.
__October 2013__ - RFC 7049 (CBOR) is approved by IETF as an Internet Standard and RFC 7049 Sectio…
-
During the shepherd review, idnits came up with the following:
== Unused Reference: 'RFC8746' is defined on line 2560, but no explicit
reference was found in the text
'[RFC8746] Borm…
-
Currently the CBOR decoders do not enforce canonical serialization during decoding, resulting in issues when structures are round-tripped and stored in Merklized or otherwise authenticated data struct…
-
Decoding 9-10 bytes of malformed CBOR data can cause exhaust memory and cause:
* fatal error: out of memory
* runtime: out of memory ...
Only 1 decode attempt of 9 bytes is required to exhaust me…
-
In current `master/src/cbor/encoding.c` line 140, there appears to be a constant encoded value for 16-bit float NaN value as `0x00e700`. I think this is a typo as RFC 7049 in Section 3.9 states that
…
-
Consider this CBOR data:
* tag number 0
-
It is possible to add a CBOR encoder and decoder to the list of supported ones:
content-type : `application/cbor`
candidate library: https://github.com/fxamacker/cbor
-
# 🐞 Bug Report
### Affected Services
The issue is located in:
edgex-go/internal/core/data/io.go
```
// Read reads and converts the request's CBOR event data into an Event stru…
-
Decoding 9-10 bytes of malformed CBOR data can cause "fatal error: out of memory" and "runtime: out of memory" errors. Only 1 decode attempt is required to cause the error.
cc @david415 @muesli
…