Skip to content
Fencer Intel
low 2.1

CVE-2014-4039 json

ppc64-diag 2.6.1 uses 0775 permissions for /tmp/diagSEsnap and does not properly restrict permissions for /tmp/diagSEsnap/snapH.tar.gz, whi…

published 12y ago modified 4mo ago also EUVD-2014-3970

cvss
2.1
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 31%
public exploits
0
none known

Summary

ppc64-diag 2.6.1 uses 0775 permissions for /tmp/diagSEsnap and does not properly restrict permissions for /tmp/diagSEsnap/snapH.tar.gz, which allows local users to obtain sensitive information by reading files in this archive, as demonstrated by /var/log/messages and /etc/yaboot.conf.

Patch / fix

  • ppc64-diag Debian 14, Debian 12 2.7.1-5

debian advisories DEBIAN-CVE-2014-4039

  • ppc64-diag RHEL 7 2.6.7-6.el7
  • ppc64-diag RHEL 6 2.6.7-4.el6

red hat advisories RHSA-2015:0383RHSA-2015:1320

Is CVE-2014-4039 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 Fencer

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-4039 updated cvss 4.6

ppc64-diag: multiple temporary file races

  • Red Hat Enterprise Linux Server (v. 6) ppc64-diag 2.6.7-4.el6
    fixed: vendor fix RHSA-2015:1320
  • Red Hat Enterprise Linux Server (v. 7) ppc64-diag 2.6.7-6.el7
    fixed: vendor fix RHSA-2015:0383

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.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

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.