Bug 973728 (CVE-2013-4166)
Summary: | CVE-2013-4166 evolution: incorrect selection of recipient gpg public key for encrypted mail | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Yves-Alexis Perez <corsac> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | herrold, jrusnack, mbarnes, mcrha, security-response-team |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-26 22:52:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 987108, 990380 | ||
Bug Blocks: | 974906, 988954 |
Description
Yves-Alexis Perez
2013-06-12 14:57:06 UTC
I fixed the bracketing issue upstream in time for E-D-S 3.9.5 and 3.8.4: https://git.gnome.org/browse/evolution-data-server/commit/?id=5d8b92c622f6927b253762ff9310479dd3ac627d https://git.gnome.org/browse/evolution-data-server/commit/?h=gnome-3-8&id=f7059bb37dcce485d36d769142ec9515708d8ae5 The multiple match issue is something I'll be more willing to deal with once I port Camel to use GPGME instead of parsing raw gpg console output over pipes. Since this is now public per commit to the repository, I'll request a CVE from oss-sec. I'm going to turn this into an SRT bug so this can be properly tracked. Do we know when this was introduced? Or has Evolution since forever had this issue? Created evolution tracking bugs for this issue: Affects: fedora-all [bug 987108] (In reply to Vincent Danen from comment #5) > Do we know when this was introduced? Or has Evolution since forever had > this issue? It's present in the 1.5 releases from 2004. That's as far back as I checked. So effectively it's been there forever. This was assigned CVE-2013-4166 as per http://seclists.org/oss-sec/2013/q3/191 This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2013:1540 https://rhn.redhat.com/errata/RHSA-2013-1540.html Statement: Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. |