Descrizione
The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard Authorization header (Bearer/Basic/OAuth) — plus every other header, including the allowlisted API-key headers — to the attacker-controlled authority. This breaks the project's own cross-transport invariant (SECURITY.md §8, OkHttpPostRedirectHeaderLeakTest) that credentials are stripped on cross-authority redirects even when redirects are followed. The sibling JDK and OkHttp/Android transports strip Authorization; Vert.x uniquely does not. This is a "fix introduced the bug" variant — the follower was added by the GHSA-9rhm hardening PR (3ae82912, refined by a5e76a0b).
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 7.5, EPSS 0.4% (percentile 32).
Versioni da aggiornare
- a2a-java a2a-java-sdk-http-client-vertx: vulnerabili le versioni dalla
1.3.2.Finalfino alla1.4.0.Finalinclusa → aggiornare a una release successiva alla1.4.0.Final.
Indicazioni del vendor
Soluzione (testo originale del vendor):
Upgrade to 1.5.0.Final or later. PR #1255 applies the shared RedirectHeaderPolicy to explicitly enabled, one-hop synchronous POST redirects across the JDK, Vert.x, and Android HTTP clients. The policy strips Authorization and the allowlisted API-key headers when a redirect crosses authorities. The reporter reviewed the proposed fix and confirmed that it addresses the reported issue.
Workaround (testo originale del vendor):
On affected versions, leave PostBuilder.followRedirects(false) (the default) so the SDK does not re-issue POST requests to redirect targets.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ruotare credenziali e chiavi, limitare l'accesso di rete al servizio e verificare accessi effettuati con credenziali predefinite.
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.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| a2a-java | a2a-java-sdk-http-client-vertx | ≥ 1.3.2.Final ≤ 1.4.0.Final | — |