You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When slicing a string, you get a panic if you do so at any point
other than at a character boundary. This happened in the
implementation of UTCTime parsing.
This bug was introduced in bc156c3,
and appears to affect only version 0.6.0.
I've tried using the clippy::string_slice lint to confirm that there
are not any other string slices in this code.
Fixes bug acw#27. Found via fuzzing.
Hello, I hope this is the right place to report this; I didn't find any documentation for a preferred method for reporting security issues.
The following code panics when trying to parse an invalid UTCTime object:
The panic occurs because of these line in lib.rs:
If the string is constructed in such a way that the first two bytes do not end on a character boundary, the slice operation will panic.
Found by fuzzing a downstream library.
I'll submit a patch ASAP.
The text was updated successfully, but these errors were encountered: