CyberRota Analysis
AI-GeneratedLemur versions prior to 1.9.2 are vulnerable due to improper handling of password updates, allowing administrator-initiated changes to be stored in plaintext. This flaw can lead to immediate exposure of user credentials if database access is compromised, as bcrypt verification fails on unhashed values. Organizations using Lemur for TLS certificate management should prioritize upgrading to version 1.9.2 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.