CyberRota Analysis
AI-GeneratedThe vulnerability affects the Lemur tool for managing TLS certificate creation in versions prior to 1.9.3, where improper handling of CertificatePermission checks allowed plugins that do not require a private key to potentially access sensitive key material. While immediate exposure was limited to public certificate data, the flaw could lead to future risks if a plugin were to misuse the private key. Organizations using Lemur for TLS management should prioritize updating to version 1.9.3 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, CertificateExport placed its CertificatePermission ownership check inside the plugin.requires_key branch for POST /api/1/certificates//export. A plugin declaring requires_key false bypassed that check, and the handler still passed cert.private_key as an argument and recorded a key_view audit event. The bundled JavaTruststoreExportPlugin ignored the key, so the immediate exposure was limited to public certificate material and misleading audit entries, but a future plugin could have consumed the supplied key. The fix passes no private key to plugins that do not require one and confines ownership checks and key_view logging to actual private-key exports. This issue is fixed in version 1.9.3.