CVE-2014-3495 json
duplicity 0.6.24 has improper verification of SSL certificates
published 2019-12-13 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-3500
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
duplicity 0.6.24 has improper verification of SSL certificates
Patch / fix
- duplicity Debian 14, Debian 13, Debian 12 0.6.21-1
debian advisories DEBIAN-CVE-2014-3495
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-2014-3495 updated cvss 4.3
duplicity: improper verification of SSL certificates
-
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
0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-3495 referenced PoC, tagged "exploit" by a source, unverified
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
- duplicity duplicity
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2014-3495
exploit, issue-tracking
-
security-tracker.debian.org
/tracker/CVE-2014-3495
third-party-advisory
-
bugzilla.suse.com
/show_bug.cgi?id=CVE-2014-3495
issue-tracking, third-party-advisory
-
access.redhat.com
/security/cve/cve-2014-3495
broken-link, third-party-advisory
Sources
- CVE List CVE-2014-3495
- NVD CVE-2014-3495
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.