Investigate fuzzer bug #35059

[sffc]

oss-fuzz filed the following report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=35059

CC @gnrunge @echeran -- are you interested in looking at this? If not, I can put it on my plate.

[gnrunge]

Not at this time, sorry. BTW, I don't have permission to view the findings. Norbert

…

On Tue, Jun 8, 2021 at 1:15 PM Shane F. Carr ***@***.***> wrote: oss-fuzz filed the following report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=35059 CC @gnrunge <https://github.com/gnrunge> @echeran <https://github.com/echeran> -- are you interested in looking at this? If not, I can put it on my plate. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#87>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJZZMHLSARDNLA7JGHSVZRDTRZ24VANCNFSM46KUT55A> .

[echeran]

Yeah, similar to Norbert, I can't see the issue, and I should start taking a look at properties-related ICU bugs this week.

[sffc]

Here is the test case in bytes:

62 4E E9 BE E2 BA 00 00 00 EA A1 4D EA E1 80 A9 E2 00 41 00 00 00 00 00 EA E1 80 A9 E2 00 00 00 00 2E 00 00 00 00 00 00 00 00 3C A9 E9 EA E1 80 A9 E2 00 00 00 00 99 EA 99 00 00 00 00 41 00 00 00 00 00 EA E1 80 A9 E2 00 00 00 00 00 00 00 00 00 00 00 00 3C 4C 00 00 EA

Note that the string ends with a UTF-8 lead byte. We should not read past the end of the string, but perhaps we should investigate.

[sffc]

oss-fuzz closed the issue with comment:

ClusterFuzz testcase 4553018782646272 is flaky and no longer crashes, so closing issue.