Skip to content

Handle invalid CBOR content like [ 0x84 ] (incomplete array) #240

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.

Sign up for GitHub

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

Jump to bottom
Closed
cowtowncoder opened this issue Jan 30, 2021 · 0 comments
Closed

Handle invalid CBOR content like [ 0x84 ] (incomplete array) #240

cowtowncoder opened this issue Jan 30, 2021 · 0 comments
Labels
cbor
Milestone
2.12.2

Comments

@cowtowncoder
Copy link
Member

(inspired by FasterXML/jackson-databind#3032)

Looks like there are types of invalid documents that do not trigger decoding exception for parser, but should.
@cowtowncoder cowtowncoder mentioned this issue Jan 30, 2021
Closed
@cowtowncoder cowtowncoder modified the milestones: 2, 2.12.2 Jan 30, 2021
@cowtowncoder cowtowncoder changed the title Handle invalid CBOR content like [ 0x84 ] (single byte doc) Handle invalid CBOR content like [ 0x84 ] (incomplete array) Jan 30, 2021
cowtowncoder added a commit that referenced this issue Jan 30, 2021
@cowtowncoder
and update release notes too wrt #240
c363acf
cowtowncoder added a commit that referenced this issue Jan 30, 2021
@cowtowncoder
Bit more work for #236 and #240
ab4f329
cowtowncoder added a commit that referenced this issue Jan 30, 2021
@cowtowncoder
Complete error reporting improvements (mostly for #240)
6bf8509
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cbor
Projects
None yet
Milestone
2.12.2
Development

No branches or pull requests
1 participant
@cowtowncoder