Lemur: Plaintext password storage in Lemur user-update path
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Netflix | lemur | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Netflix | Lemur |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-q437-g7fv-2jvv | Lemur user-update path stores plaintext passwords |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.289% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Netflix
Netflix lemur |
|
| Vendors & Products |
Netflix
Netflix lemur |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Lemur manages TLS certificate creation. Prior to 1.9.2, lemur.users.service.update assigned a replacement password directly to users.password, while lemur/users/models.py registered User.hash_password only for the before_insert event. Because no before_update listener ran, administrator-initiated password changes through PUT /api/1/users/ were committed as plaintext. The affected user could no longer authenticate normally because bcrypt verification received an unhashed value. A database, backup, replica, query-log, or administrative read compromise exposed immediately usable credentials without offline cracking. The fix registers hashing for before_update and avoids rehashing values that already have a bcrypt prefix. This issue is fixed in version 1.9.2. | |
| Title | Lemur: Plaintext password storage in Lemur user-update path | |
| Weaknesses | CWE-256 | |
| References |
| |
| Metrics |
cvssV3_1
|