Skip to content
Fencer Intel
medium 5.0

CVE-2014-4040 json

snap in powerpc-utils 1.2.20 produces an archive with fstab and yaboot.conf files potentially containing cleartext passwords, and lacks a w…

published 2014-06-17 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-3971

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

snap in powerpc-utils 1.2.20 produces an archive with fstab and yaboot.conf files potentially containing cleartext passwords, and lacks a warning about reviewing this archive to detect included passwords, which might allow remote attackers to obtain sensitive information by leveraging access to a technical-support data stream.

Patch / fix

  • powerpc-utils Debian 14, Debian 13, Debian 12 1.3.1-2

debian advisories DEBIAN-CVE-2014-4040

  • powerpc-utils RHEL 7 1.2.24-7.el7

red hat advisories RHSA-2015:0384

  • powerpc-utils Linux Micro 6.1 1.3.12-slfo.1.1_5.1
  • powerpc-utils SLES for SAP 12, SLES 12 1.2.22-7.1

suse advisories SUSE-SU-2025:21067-1SUSE-SU-2015:0232-1

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-4040 updated cvss 1.2

powerpc-utils: snap creates archives with fstab and yaboot.conf which may expose certain passwords

  • Red Hat Enterprise Linux 6 powerpc-utils
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Server (v. 7) powerpc-utils 1.2.24-7.el7
    fixed: vendor fix RHSA-2015:0384

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

1.83% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness

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.