CVE-2014-5254 json
xcfa before 5.0.1 creates temporary files insecurely which could allow local users to launch a symlink attack and overwrite arbitrary files.
published 6y ago modified 4mo ago also EUVD-2014-5147
- cvss
- 4.7
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
xcfa before 5.0.1 creates temporary files insecurely which could allow local users to launch a symlink attack and overwrite arbitrary files.
Patch / fix
- xcfa_project xcfa 5.0.1
- xcfa Debian 14, Debian 13, Debian 12 5.0.1-1
debian advisories DEBIAN-CVE-2014-5254
Is CVE-2014-5254 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.debian.org https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756600 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 3.3 | AV:L/AC:M/Au:N/C:N/I:P/A:P |
Affected products
- xcfa xcfa
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=756600
exploit, mailing-list, third-party-advisory
-
security-tracker.debian.org
/tracker/CVE-2014-5254
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95331
third-party-advisory, vdb-entry
-
openwall.com
/lists/oss-security/2014/08/15/4
mailing-list, third-party-advisory
-
securityfocus.com
/bid/69020
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2014-5254
- NVD CVE-2014-5254
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.