CVE-2014-2387 json
Pen 0.18.0 has Insecure Temporary File Creation vulnerabilities
published 2019-12-13 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2423
- cvss
- 4.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Pen 0.18.0 has Insecure Temporary File Creation vulnerabilities
Patch / fix
- pen Debian 14, Debian 13, Debian 12 0.22.1-1
debian advisories DEBIAN-CVE-2014-2387
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-2387 updated cvss 2.1
pen: insecure temporary file use flaws
-
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.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
security-tracker.debian.org
/tracker/CVE-2014-2387
third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2014-2387
issue-tracking, third-party-advisory
-
bugzilla.suse.com
/show_bug.cgi?id=CVE-2014-2387
issue-tracking, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/91992
third-party-advisory, vdb-entry
-
openwall.com
/lists/oss-security/2014/03/13/5
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2014/03/14/2
mailing-list
-
securityfocus.com
/bid/66214
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2014-2387
- NVD CVE-2014-2387
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.