Bug 818922 - evolution-data-server: Improper certificate validation in Evolution calendar caldav and addressbook webdav contact back-ends
Summary: evolution-data-server: Improper certificate validation in Evolution calendar ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 637433
Blocks: 818923
TreeView+ depends on / blocked
 
Reported: 2012-05-04 11:09 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 17:12:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Lieskovsky 2012-05-04 11:09:51 UTC
It was found that evolution-data-server, a back-end contacts, tasks and calendar information handling data server for Evolution, did not perform SSL certificates validation for secured connections. Evolution email client, using evolution-data-server's calendar caldav and addressbook webdav contact back-ends, holding the trust about the other side of the connection being the valid owner of the presented certificate, could be tricked into accepting a spoofed SSL certificate by mistake (MITM attack).

Upstream bug report:
[1] https://bugzilla.gnome.org/show_bug.cgi?id=671537

References:
[2] https://bugzilla.novell.com/show_bug.cgi?id=760517
[3] https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/933659/
[4] http://www.openwall.com/lists/oss-security/2012/05/03/3
[5] http://www.openwall.com/lists/oss-security/2012/05/04/4
[6] http://www.openwall.com/lists/oss-security/2012/05/04/5

Upstream patches:
[7] https://bugzilla.gnome.org/show_bug.cgi?id=671537#c10
    (patch for evolution-data-server)
[8] https://bugzilla.gnome.org/attachment.cgi?id=209771
    (patch for evolution)

Comment 1 Josh Bressers 2014-06-13 17:12:05 UTC
This issue is known upstream.


Note You need to log in before you can comment on or make changes to this bug.