Netflix Lemur
Lemur: Unchecked `replaces[]` lets any user silence notifications and hijack auto-rotation for arbitrary certificates
Lemur manages TLS certificate creation. From 0.5.0 until 1.9.3, certificate create, upload, and edit requests accepted replaces[] or replacements identifiers that AssociatedCertificateSchema resolved with fetch_objects without a CertificatePermission check. Assigning those objects to Certificate.replaces invoked an append listener that disabled the victim certificate notifications and marked it as replaced. The victim was then excluded from get_all_pending_reissue, and certificate_rotate could deploy the attacker certificate to endpoints serving the victim. An authenticated non-read-only user could target certificates for which the user had no ownership or role, suppress lifecycle automation, and cause fleet-wide TLS disruption or unauthorized substitution. The fix authorizes every referenced replacement certificate before mutation. This issue is fixed in version 1.9.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.5.0, < 1.9.3
Fixed in 1.9.3
Mitigation
Upgrade lemur to 1.9.3 or later.
References
- Vendor advisory github.com/Netflix/lemur/security/advisories/G…
- Patch github.com/Netflix/lemur/commit/28687453516095…
- Release notes github.com/Netflix/lemur/releases/tag/v1.9.3
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.