Skip to content
Fencer Vulns
high 7.2

CVE-2008-5188 json

The (1) ecryptfs-setup-private, (2) ecryptfs-setup-confidential, and (3) ecryptfs-setup-pam-wrapped.sh scripts in ecryptfs-utils 45 through…

published 2008-11-21 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-5166

cvss
7.2
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 32%
public exploits
0
none known

Summary

The (1) ecryptfs-setup-private, (2) ecryptfs-setup-confidential, and (3) ecryptfs-setup-pam-wrapped.sh scripts in ecryptfs-utils 45 through 61 in eCryptfs place cleartext passwords on command lines, which allows local users to obtain sensitive information by listing the process.

Patch / fix

  • ecryptfs-utils Debian 14, Debian 13, Debian 12 66-1

debian advisories DEBIAN-CVE-2008-5188

  • ecryptfs-utils RHEL 5 75-5.el5
  • ecryptfs-utils-gui RHEL 5 75-5.el5

red hat advisories RHSA-2009:1307

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-2008-5188 updated cvss 2.1

ecryptfs-utils: potential provided password disclosure in the process table

  • Red Hat Enterprise Linux (v. 5 server) ecryptfs-utils 75-5.el5, ecryptfs-utils-gui 75-5.el5 Red Hat Enterprise Linux Desktop (v. 5 client) ecryptfs-utils 75-5.el5, ecryptfs-utils-gui 75-5.el5 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) ecryptfs-utils 75-5.el5, ecryptfs-utils-gui 75-5.el5
    fixed: vendor fix RHSA-2009:1307

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

CVSS scores

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

Classification

Weakness
  • CWE-255 Credentials Management Errors

References

Sources

Fencer Vulns 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.