Steeltoe.Security.Authorization.Certificate
Affected
- introduced
0, fixed4.3.0(ecosystem)
Fixed versions
4.3.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-81868
Steeltoe: Header-forwarded client cert lacks proof of private-key possession
Summary
When Steeltoe's certificate-based authorization (UseCertificateAuthorization) is configured, the default configuration of the middleware relies on the X-Client-Cert HTTP header to identify the client certificate, without verifying private-key possession. This header is not stripped by common Cloud Foundry routers (like Gorouter or Envoy) on inbound requests.
Impact
An attacker who obtains the public certificate of an application instance in the target organization or space can spoof the X-Client-Cert header. This allows the attacker to bypass SameOrg and SameSpace authorization policies, granting unauthorized access to protected endpoints for the duration of the certificate's validity period.
Affected configuration
AddOrgAndSpacePolicies() and UseCertificateAuthorization() for inter-service authorization.Mitigations
If an immediate upgrade to a patched version is not possible:
UseCertificateForwarding to trusted proxy source IPs using ForwardedHeadersOptions.KnownProxies and KnownNetworks.X-Forwarded-Client-Cert so that Cloud Foundry Gorouter and Envoy header stripping mechanisms apply to inbound untrusted requests..apps.internal) and container-to-container network policies to strictly limit network access to intended internal clients.Medium Basis: The source's own band: MODERATE
0, fixed 4.3.0 (ecosystem)4.3.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0