Aller au contenu
en Se connecter
5.1 Moyenne

CVE-2026-107597 PIA's token verification (`verify_token` in `pia/oidc.py`) fetches the OIDC discovery document of an allowlisted…

Description

PIA's token verification (`verify_token` in `pia/oidc.py`) fetches the OIDC discovery document of an allowlisted issuer and then follows the `jwks_uri` contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty (`pia/oidc.py:42-52`). An approved identity provider — and every registered per-project Jenkins instance under `https://ci.eclipse.org/<project>/oidc` is a separate such party (`pia/models.py`) — can therefore direct PIA to issue a GET request to an arbitrary host and port, including over plaintext `http`, from PIA's own network position. The fetch happens before any signature is verified, as a side effect of an unauthenticated `POST /v1/upload/sbom` request that is ultimately rejected with 401.

Produits et versions touchés

Produit Versions touchées Corrigé en
Eclipse CSI - PIA 0.8 premières → 0.8.0 Pas de correctif indiqué

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Eclipse CSI - PIA

Les 5 CVE de Eclipse CSI - PIA →
CVE-2026-108062 Pre-authentication OIDC discovery and JWKS fetches run synchronously on the asyncio event loop, so one unauthenticated… 6.9 Moyenne CVE-2026-18353 PIA's `POST /v1/upload/sbom` endpoint accepts a Bearer JWT and checks its **unverified** `iss` claim against an issuer… 8.8 Élevée CVE-2026-14336 PIA's OIDC issuer allowlist for Jenkins tokens uses a bare string-prefix check (issuer.startswith('… 8.2 Élevée CVE-2026-12616 The /v1/upload/sbom endpoint extracts the iss claim from the attacker-supplied JWT with signature verification disabled,… 6.9 Moyenne
Suivre cette CVE