Dear security team,
so far there hasn't been a security update for the latest evolution
vulnerabilities. (CVE-2005-2549/CVE-2005-2550)
I've attached patches for Woody and Sarge. The Sarge fixes are straightforward,
but some comments on Woody, relative to the patch hunks from the Sarge fix:
- accum_attribute() isn't present in Woody, so hunk 1-3 are void.
- the vulnerable code from e-cal-component-preview.c isn't present either.
- the vulnerable code from e-calendar-table.c and e-calendar-view.c is contained
in Woody, although in a different place. This is exploitable as well, have a
look at the description of the function that feeds data into ical_string:
| * cal-client/cal-client.c (cal_client_get_component_as_string): new
| function to return a complete VCALENDAR string containing a VEVENT
| or VTODO with all the VTIMEZONEs it uses.
Dear security team, 2549/CVE- 2005-2550) -preview. c isn't present either. cal-client. c (cal_client_ get_component_ as_string) : new
so far there hasn't been a security update for the latest evolution
vulnerabilities. (CVE-2005-
I've attached patches for Woody and Sarge. The Sarge fixes are straightforward,
but some comments on Woody, relative to the patch hunks from the Sarge fix:
- accum_attribute() isn't present in Woody, so hunk 1-3 are void.
- the vulnerable code from e-cal-component
- the vulnerable code from e-calendar-table.c and e-calendar-view.c is contained
in Woody, although in a different place. This is exploitable as well, have a
look at the description of the function that feeds data into ical_string:
| * cal-client/
| function to return a complete VCALENDAR string containing a VEVENT
| or VTODO with all the VTIMEZONEs it uses.
Cheers,
Moritz