CVE-2010-4533 json
offlineimap before 6.3.4 added support for SSL server certificate validation but it is still possible to use SSL v2 protocol, which is a fl…
published 2019-11-13 6 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4501
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
offlineimap before 6.3.4 added support for SSL server certificate validation but it is still possible to use SSL v2 protocol, which is a flawed protocol with multiple security deficiencies.
Patch / fix
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-2010-4533 updated cvss 4.3
OfflineIMAP: Disable SSLv2 protocol
-
Red Hat All currently supported Red Hat productsnot 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
1.03% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- offlineimap offlineimap
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
openwall.com
/lists/oss-security/2010/12/23/2
mailing-list, patch, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2010-4533
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2010-4533
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2010-4533
not-applicable
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=606962
third-party-advisory
Sources
- CVE List CVE-2010-4533
- NVD CVE-2010-4533
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.