CVE-2013-4166 json
The gpg_ctx_add_recipient function in camel/camel-gpg-context.c in GNOME Evolution 3.8.4 and earlier and Evolution Data Server 3.9.5 and ea…
published 2020-02-06 6 y ago modified 2026-06-16 4 mo ago also EUVD-2013-4091
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
The gpg_ctx_add_recipient function in camel/camel-gpg-context.c in GNOME Evolution 3.8.4 and earlier and Evolution Data Server 3.9.5 and earlier does not properly select the GPG key to use for email encryption, which might cause the email to be encrypted with the wrong key and allow remote attackers to obtain sensitive information.
Patch / fix
- evolution RHEL 6 2.32.3-30.el6
- ekiga RHEL 6 3.2.6-4.el6
- finch RHEL 6 2.7.9-11.el6
- totem RHEL 6 2.28.6-4.el6
- cheese RHEL 6 2.28.1-8.el6
- pidgin RHEL 6 2.7.9-11.el6
- planner RHEL 6 0.14.4-10.el6
- gtkhtml3 RHEL 6 3.32.2-2.el6
red hat advisories RHSA-2013:1540
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4166 updated cvss 1.2
evolution: incorrect selection of recipient gpg public key for encrypted mail
-
Red Hat Enterprise Linux 5 evolutionaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux Desktop (v. 6) ekiga 3.2.6-4.el6, totem 2.28.6-4.el6, cheese 2.28.1-8.el6, pidgin 2.7.9-11.el6, libgdata 0.6.4-2.el6, openchange 1.0-6.el6, +23 more Red Hat Enterprise Linux Desktop Optional (v. 6) finch 2.7.9-11.el6, totem 2.28.6-4.el6, pidgin 2.7.9-11.el6, libgdata 0.6.4-2.el6, openchange 1.0-6.el6, gtkhtml3 3.32.2-2.el6, +27 more Red Hat Enterprise Linux HPC Node (v. 6) gnome-python2-desktop 2.28.0-5.el6, gnome-python2-gnomekeyring 2.28.0-5.el6 Red Hat Enterprise Linux HPC Node Optional (v. 6) libgdata 0.6.4-2.el6, gnome-panel 2.30.2-15.el6, control-center 2.28.1-39.el6, gnome-panel-libs 2.30.2-15.el6, gnome-python2-rsvg 2.28.0-5.el6, gnome-python2-totem 2.28.0-5.el6, +15 more Red Hat Enterprise Linux Server (v. 6) totem 2.28.6-4.el6, cheese 2.28.1-8.el6, libgdata 0.6.4-2.el6, totem-upnp 2.28.6-4.el6, gnome-panel 2.30.2-15.el6, totem-nautilus 2.28.6-4.el6, +13 more Red Hat Enterprise Linux Server Optional (v. 6) ekiga 3.2.6-4.el6, finch 2.7.9-11.el6, totem 2.28.6-4.el6, pidgin 2.7.9-11.el6, openchange 1.0-6.el6, gtkhtml3 3.32.2-2.el6, +29 morefixed: vendor fix RHSA-2013:1540
+2 more productsfewer
Red Hat Enterprise Linux Workstation (v. 6) ekiga 3.2.6-4.el6, totem 2.28.6-4.el6, cheese 2.28.1-8.el6, pidgin 2.7.9-11.el6, libgdata 0.6.4-2.el6, openchange 1.0-6.el6, +23 more Red Hat Enterprise Linux Workstation Optional (v. 6) finch 2.7.9-11.el6, totem 2.28.6-4.el6, pidgin 2.7.9-11.el6, openchange 1.0-6.el6, gtkhtml3 3.32.2-2.el6, planner 0.14.4-10.el6, +25 more
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- GNOME Evolution
- GNOME Evolution Data Server
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
git.gnome.org
/browse/evolution-data-server/commit/?h=gnome-3-8&id=f7059bb37dcce485d36d769142ec9515708d8ae5
patch, vendor-advisory
-
git.gnome.org
/browse/evolution-data-server/commit/?id=5d8b92c622f6927b253762ff9310479dd3ac627d
patch, vendor-advisory
-
seclists.org
/oss-sec/2013/q3/191
mailing-list, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=973728
issue-tracking, third-party-advisory
-
rhn.redhat.com
/errata/RHSA-2013-1540.html
third-party-advisory
Sources
- CVE List CVE-2013-4166
- NVD CVE-2013-4166
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.