Details
Source artifact: audit/harnesses/public-repo-threat-model-harness/results/netflix-lemur-100run-mythos-20260627T051129Z/findings.jsonl (run_050, finding cluster lemur-revoke-via-duplicate, 2/100 runs).
Suggested fix
Decouple CA-side revocation authority from Lemur row ownership:
- On
POST /certificates/upload, ifauthorityis supplied enforceAuthorityPermissionfor that authority, and reject/ignore caller-suppliedexternal_id. - Before calling
plugin.revoke_certificate, look up allCertificaterows sharing the same(authority_id, serial)orbodyand requireCertificatePermissionon every match (and run the endpoint-attached check against all matches). - Consider a DB uniqueness constraint or dedup on
(authority_id, serial)so a second row for the same CA-issued certificate cannot be created. - Stop exposing
external_idinCertificateOutputSchemato non-owners.