Descrizione
A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 7.3, EPSS 0.3% (percentile 29).
Versioni da aggiornare
Il record non riporta ancora i prodotti e le versioni corrette (analisi NVD in corso). Consultare l'advisory del vendor nei riferimenti.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Applicare filtri sul traffico in uscita del server e bloccare l'accesso agli endpoint di metadati cloud (169.254.169.254).
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Riferimenti
- Riferimentohttps://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282
- Riferimentohttps://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8
- Riferimentohttps://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a
- Riferimentohttps://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061
- Riferimentohttps://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90
- Riferimentohttps://github.com/temporalio/temporal-proxy/pull/284
- Riferimentohttps://github.com/temporalio/temporal-proxy/pull/292
- Riferimentohttps://github.com/temporalio/temporal-proxy/pull/293
- Riferimentohttps://github.com/temporalio/temporal-proxy/pull/294
- Riferimentohttps://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2
- Riferimentohttps://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2
- Riferimentohttps://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1