You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 13fb885
Browse filesBrowse the repository at this point in the historyBrowse files
CP-25960: allowlist and require HTTPS for discovery-derived hosts
Service discovery handed the identity, discoverycontext and secrets_manager
API hosts straight from the response body to the clients that POST the agent's
ServiceAccount token, with no constraint on where those hosts pointed.
Constrain each discovered host to a known CyberArk root domain, or to the host
the discovery call itself was addressed to, and require https. A host that
fails either check is dropped and treated as absent from the response. A
rejected identity host now reports that specifically rather than claiming the
tenant may be suspended.
Also stop the authn-jwt exchange error carrying Conjur's response body, which
reached a Kubernetes Pod Event readable by anyone with 'get events' in the
namespace. The body is logged at V(2) instead.
Note that the allowlist constrains a misbehaving or compromised discovery
service. It is not a defence against an attacker who can already terminate TLS
for the discovery host, since such an attacker can intercept any permitted host
equally well.
Two follow-ups are recorded on the pull request and remain open: the new
identity-rejection error still embeds the untrusted URL on the same Pod Event
path, and the upload path still embeds upstream response bodies.
return"", fmt.Errorf("authn-jwt exchange rejected (%d); verify service_id, the authenticator is enabled, and the SA token audience is 'conjur' (run with -v=2 to see Conjur's response body)",
0 commit comments