Summary
Lemur contains a server-side request forgery vulnerability in authority updates, where an authorized user can replace a stored ACME directory URL without the validation applied during authority creation. When a later certificate issuance uses that URL, the backend may send requests to internal services or cloud metadata endpoints.
Affected context
The issue occurs in Lemur deployments where authority options can be updated through the authority API and the resulting ACME URL is later used by the backend during certificate issuance. It is relevant when update operations bypass the host allowlist or equivalent URL validation enforced during initial authority creation.
Exploit preconditions
- Attack surface: The authority update API and subsequent certificate issuance workflow - Required access: An authenticated account with authority-management privileges - Trigger point: Updating the stored ACME URL, followed by an issuance operation - Why exploitation is possible: The update path accepts the new URL without reapplying the creation-time host validation, allowing backend-controlled outbound requests to destinations selected by the authorized user
Why this happens
The underlying bug is inconsistent validation across create and update operations. The authority creation path enforced an ACME directory host allowlist, but the authority update path forwarded user-controlled options without applying the same check. When the stored value was later consumed by the ACME client, the backend treated an insufficiently validated URL as a trusted destination. This behavior maps to CWE-918, Server-Side Request Forgery, because attacker-influenced input controls a server-side network request.
Potential impact
- The backend may access internal services that are unreachable from outside the deployment.
- Cloud instance metadata or temporary credentials could be exposed.
- Internal service responses could be disclosed to an authorized attacker, depending on response handling.
- Network segmentation assumptions could be weakened through backend-originated requests.
- Certificate issuance workflows could be disrupted or redirected to unintended ACME services.
General mitigation guidance
Mitigation generally focuses on applying the same destination-validation policy to every lifecycle operation, including creation, update, import, and runtime use. ACME URLs should be accepted only from an explicit, narrowly scoped allowlist and should be parsed and normalized before validation. Backend request clients can further reduce trust by restricting redirects, permitted schemes, destination ports, and resolution of private or link-local addresses. Egress filtering, network policies, isolated service accounts, and least-privilege permissions provide defense in depth. Validation should occur before persistence and again at the point of use where configuration may have changed.
How teams detect issues like this
Detection approaches include static analysis and taint tracking for user-controlled URL values that reach HTTP client or ACME directory APIs. Code review should compare validation behavior across create, update, import, and execution paths, with particular attention to persisted configuration values. Runtime monitoring can alert on backend requests to private, loopback, link-local, or otherwise disallowed address ranges. Policy enforcement may include outbound firewall rules, DNS and IP destination controls, and automated security checks for missing URL allowlist validation.

