-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cbor_value_map_find_value may crash with invalid input #167
Comments
Ran it now. Results in the following: Assertion failed: (it->type != CborInvalidType), function cbor_value_advance, file
/Users/tsonono/repos/cbor-c-test/app/external/tinycbor/src/cborparser.c, line 526. |
Added a test, cannot reproduce in 0.6 (dev branch). |
Seems it got fixed by 2b2d663. |
thiagomacieira
added a commit
to thiagomacieira/tinycbor
that referenced
this issue
Oct 15, 2019
If a map end (Break byte) occurs before we've read the concrete item for the value, then the map is invalid. Fixes intel#167 Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
thiagomacieira
added a commit
to thiagomacieira/tinycbor
that referenced
this issue
Oct 15, 2019
If a map end (Break byte) occurs before we've read the concrete item for the value, then the map is invalid. Fixes intel#167 Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
thiagomacieira
added a commit
to thiagomacieira/tinycbor
that referenced
this issue
Oct 15, 2019
If a map end (Break byte) occurs before we've read the concrete item for the value, then the map is invalid. Fixes intel#167 Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
thiagomacieira
added a commit
that referenced
this issue
Oct 22, 2019
If a map end (Break byte) occurs before we've read the concrete item for the value, then the map is invalid. Fixes #167 Signed-off-by: Thiago Macieira <thiago.macieira@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The last
VERIFY_CBOR
is expected to fail, but not crash.@TSonono
The text was updated successfully, but these errors were encountered: