-
Notifications
You must be signed in to change notification settings - Fork 150
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
CalDav POST collection-url -> http-3.0 crash #2346
Comments
@ksmurchison, looks like this crash is occurring in here: cyrus-imapd/imap/http_caldav.c Lines 2920 to 2925 in 7854ec6
Note that This function is quite different on master, but looks like it might be susceptible to a similar crash: cyrus-imapd/imap/http_caldav.c Lines 3422 to 3423 in d00d029
Note that What should It looks like both versions of |
Looks like 2.5 is not affected by this: it threw a HTTP_BAD_REQUEST error when no uid was found: cyrus-imapd/imap/http_caldav.c Lines 2518 to 2531 in c805d3e
|
I'm looking at the current libical source on our fork, and if I'm reading it correctly, it looks like it should detect a missing uid as invalid. @dilyanpalauzov, which version of libical do you have there? |
Providing that the POST is supposed to create an URL for the object and it is common that the UID is part of the address of the object, I was expecting that the server would generate the UID. |
I use the latest libical v3.0.3-52-ga579ed50. In In static const icalrestriction_property_record icalrestriction_property_record contains for ICAL_METHOD_NONE and ICAL_UID_PROPERTY:
in particular ICAL_VCALENDAR_COMPONENT + ICAL_UID_PROPERTY => ICAL_RESTRICTION_ZEROORONE. |
UID is s required property for a VEVENT per both RFC 5545 and 5546. The fact that icalrestriction_check() and Cyrus fail to detect that is a bug in both. Such a VEVENT should be rejected. In the case of bulk import this would result in a element containing an error. |
…al" component has a UID (resolves issue #2346)
…al" component has a UID (resolves issue #2346)
Sending
causes httpd-3.0 to crash with this backtrace:
The text was updated successfully, but these errors were encountered: