CVE-2014-3986 json
include/tests_webservers in Lynis before 1.5.5 allows local users to overwrite arbitrary files via a symlink attack on a /tmp/lynis.*.unsor…
published 12y ago modified 4mo ago also EUVD-2014-3919
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
include/tests_webservers in Lynis before 1.5.5 allows local users to overwrite arbitrary files via a symlink attack on a /tmp/lynis.*.unsorted file with an easily determined name.
Patch / fix
- lynis Debian 14, Debian 13, Debian 12 1.5.5-1
debian advisories DEBIAN-CVE-2014-3986
Is CVE-2014-3986 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 FencerVendor 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-3986 updated cvss 7.2
lynis: insecure temporary file issues leading to privilege escalation
-
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.34% chance of exploitation in the next 30 days, higher than 27% 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
- cisofy.com /files/lynis-1.5.5.tar.gz
-
openwall.com
/lists/oss-security/2014/06/07/3
mailing-list
-
openwall.com
/lists/oss-security/2014/06/05/14
mailing-list
-
seclists.org
/fulldisclosure/2014/Jun/21
mailing-list
-
openwall.com
/lists/oss-security/2014/06/06/12
mailing-list
Sources
- CVE List CVE-2014-3986
- NVD CVE-2014-3986
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.