Enterprise LinuxOperating system · Redhat
CVE-2019-3890
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt was discovered evolution-ews before 3.31.3 does not check the validity of SSL certificates. An attacker could abuse this flaw to get confidential information by tricking the user into connecting to a fake server without the user noticing the difference.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe evolution-ews component (Evolution Exchange Web Services) before version 3.31.3 fails to validate SSL certificates when establishing connections to Exchange servers. This allows an attacker performing a man-in-the-middle attack to present a fraudulent certificate, and the client will accept it without warning, enabling interception of credentials and sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 7.0= 8.0< 3.31.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify evolution-ews is installedCheck if the evolution-ews package is present on the system using package manager (e.g., rpm -qa | grep evolution-ews for RHEL, dpkg -l | grep evolution-ews for Debian-based systems)Affected if The package is installed and its version is below 3.31.3
-
Determine evolution-ews package versionQuery the installed version using the system package manager: rpm -q evolution-ews or dpkg -s evolution-ewsAffected if The version number returned is less than 3.31.3
-
Check if EWS account is configured in EvolutionLook for EWS configuration files in the user's home directory, typically under ~/.config/evolution/ or ~/.local/share/evolution/, or check for Exchange account settings in Evolution's account configurationAffected if An Exchange Web Services account is configured and the evolution-ews version is vulnerable
-
Verify SSL certificate validation behaviorAttempt to connect to an Exchange server with a self-signed or invalid SSL certificate using evolution-ews; observe whether the connection is allowed without warning or certificate errorAffected if The connection succeeds without presenting any SSL certificate validation warning despite the server presenting an invalid certificate
The system is affected if evolution-ews version is below 3.31.3 and an Exchange Web Services account is configured to connect to an Exchange server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.31.3
Upgrade evolution-ews to version 3.31.3 or later, which includes proper SSL certificate validation. Until upgraded, avoid using untrusted networks when connecting to Exchange servers.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data