Closed netfenceventu closed 1 month ago
Just an update: a second user started having the same problem on the same calendar (and now she can't see it at all in ThunderBird).
That backtrace is really helpful, thanks. Looks like this was already fixed on master by https://github.com/cyrusimap/cyrus-imapd/pull/3809
Are you able to apply the patches from that PR and see if that helps? You can get them in raw patch format by adding ".patch" to the end of the url, like this: https://github.com/cyrusimap/cyrus-imapd/pull/3809.patch
Hello and thank you very much! I had to work the patches a little, as they don't apply cleanly to 3.4, but they indeed fixed the problem.
I've got an install of 3.4.7 on FreeBSD 13.3/amd64 which has been working properly for years. Recently (possibly due to some upgrades?) it started crashing when a specific user accesses a specific shared calendar.
All the users use the same client (ThunderBird 115.10) and all the allowed users are able to use that shared calendar except that specific one. When this user's client connects to the calendar, it does not work and I see in the logs something like:
I tried removing and re-adding permissions for this calendar to this specific user: nothing changed.
So I compiled Cyrus and libical with debug info and here's the stack trace:
At frame #3 (icalparser_parse_string), it seems str is 7684 chars long, but not null-terminated.
Going up the stack, at frame #4 (propfind_caldata): fctx->msg_buf.len=8192 fctx->s is full, again without a null terminator.
Altough myself a developer, I'm not familiar with CyrusIMAP's code, so I don't know what to check. Any suggestion is welcome.