CVE-2014-1639 json
syncevo/installcheck-local.sh in syncevolution before 1.3.99.7 uses mktemp to create a safe temporary file but appends a suffix to the orig…
published 2014-01-28 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-1713
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
syncevo/installcheck-local.sh in syncevolution before 1.3.99.7 uses mktemp to create a safe temporary file but appends a suffix to the original filename and writes to this new filename, which allows local users to overwrite arbitrary files via a symlink attack on the new filename.
Patch / fix
- syncevolution Debian 14, Debian 12 1.3.99.7-1
debian advisories DEBIAN-CVE-2014-1639
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-1639 updated cvss 2.6
syncevolution: insecure temporary file usage in installcheck-local.sh
-
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.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.3 | AV:L/AC:M/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=736357
vendor-advisory
-
openwall.com
/lists/oss-security/2014/01/22/4
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/90662
vdb-entry
-
osvdb.org
/102380
vdb-entry
-
securityfocus.com
/bid/65098
vdb-entry
-
openwall.com
/lists/oss-security/2014/01/22/3
mailing-list
Sources
- CVE List CVE-2014-1639
- NVD CVE-2014-1639
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.