Skip to content
Fencer Intel
high 7.3

CVE-2011-3355 json

evolution-data-server3 3.0.3 through 3.2.1 used insecure (non-SSL) connection when attempting to store sent email messages into the Sent fo…

published 2019-11-25 6 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3319

cvss
7.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

evolution-data-server3 3.0.3 through 3.2.1 used insecure (non-SSL) connection when attempting to store sent email messages into the Sent folder, when the Sent folder was located on the remote server. An attacker could use this flaw to obtain login credentials of the victim.

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-2011-3355 updated cvss 4.3

evolution: IMAP does non-SSL connection when storing to Sent folder

  • Red Hat Enterprise Linux 4 evolution, evolution28 Red Hat Enterprise Linux 5 evolution Red Hat Enterprise Linux 6 evolution, evolution-pst, evolution-help, evolution-perl, evolution-conduits, evolution-spamassassin Red Hat Enterprise Linux 7 evolution-data-server, evolution-data-server-perl, evolution-data-server-tests, evolution-data-server-langpacks
    not affected: vulnerable code not present

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

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • openwall.com https://www.openwall.com/lists/oss-security/2011/09/09/1 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • evolution-data-server3 evolution-data-server3

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data

References

Sources

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.