CVE-2022-31085 json
Missing Encryption of Sensitive Data in ldap-account-manager
published 2022-06-27 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52742
- cvss
- 5.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
LDAP Account Manager (LAM) is a webfrontend for managing entries (e.g. users, groups, DHCP settings) stored in an LDAP directory. In versions prior to 8.0 the session files include the LDAP user name and password in clear text if the PHP OpenSSL extension is not installed or encryption is disabled by configuration. This issue has been fixed in version 8.0. Users unable to upgrade should install the PHP OpenSSL extension and make sure session encryption is enabled in LAM main configuration.
Patch / fix
- ldap-account-manager ldap_account_manager 8.0
- ldap-account-manager Debian 14, Debian 13, Debian 12 8.0.1-1
debian advisories DEBIAN-CVE-2022-31085
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- LDAPAccountManager lam
Classification
References
-
github.com
/LDAPAccountManager/lam/commit/f1d5d04952f39a1b4ea203d3964fa88e1429dfd4
patch, third-party-advisory
-
debian.org
/security/2022/dsa-5177
vendor-advisory, third-party-advisory
-
github.com
/LDAPAccountManager/lam/security/advisories/GHSA-6m3q-5c84-6h6j
third-party-advisory
Sources
- CVE List CVE-2022-31085
- NVD CVE-2022-31085
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.