CyberRota Analysis
AI-GeneratedLemur versions prior to 1.9.3 are vulnerable to a flaw that allows non-read-only users to create duplicate certificate entries, enabling them to bypass permissions and revoke legitimate certificates, potentially leading to a fleet-wide TLS denial of service. This vulnerability poses a significant risk to organizations relying on Lemur for TLS certificate management, particularly those with extensive certificate deployments. It is crucial for users of Lemur to prioritize upgrading to version 1.9.3 or later 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.3, POST /api/1/certificates/upload allowed a non-read-only user to create a duplicate row using another certificate body, authority_id, serial, or external_id without requiring permission on the underlying authority. PUT /api/1/certificates//revoke authorized the caller against only the selected Lemur row, so the creator of the duplicate bypassed CertificatePermission. The duplicate had no cert.endpoints, which also bypassed the safeguard that prevents revocation of deployed certificates. Issuer plugins then revoked the real CA-side certificate using certificate.body or external_id under the stored authority credentials. An attacker could therefore revoke arbitrary managed certificates and cause fleet-wide TLS denial of service. The fix rejects duplicate authority_id and serial identities, requires authority access on upload, and checks every matching row during revocation. This issue is fixed in version 1.9.3.