llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @sigstore/oci

GHSA-HRF4-74C9-4HR4

Registry challenge can direct credentialed token requests to arbitrary hosts

Parche disponible
Descargar PNG JSON
CVSS 3.1
4.7
Media
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -8 d de la divulgación
Exposición6 dDesde la divulgación, 13 nov 2026, 4:24 p. m.
Detección6 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 0.8.0
Monitoreo
Detectada +1
5 nov 26
13 nov 26
20 nov 26
5 nov 26
9 nov 26
13 nov 26
16 nov 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 0.8.0 @sigstore/oci · -8 d desde divulgación
Divulgación Publicada GHSA-HRF4-74C9-4HR4 divulgada · CVSS 4.7 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

`@sigstore/oci` sends token requests to whatever URL a registry names in its `WWW-Authenticate` challenge, without validating it. A malicious or compromised registry can make the client send requests to internal services or cloud metadata endpoints that the attacker can't reach directly.

Impact

Any application that uses `@sigstore/oci` to talk to a registry the attacker controls is affected. This includes `sigstore attach` in `@sigstore/cli`. The affected APIs are `getImageDigest` and `attachArtifactToImage`. To exploit it, the attacker must run or compromise the registry, or get the victim to reference an image on it.

When a registry returns `401 Unauthorized`, the `realm` parameter of its `WWW-Authenticate` header names the token endpoint. `@sigstore/oci` requests a token from that URL and sends the registry credentials in a `Basic` `Authorization` header. The client doesn't check the realm's scheme, host, or address range, so the realm can point at `127.0.0.1`, a private network address, or a metadata endpoint such as `169.254.169.254`.

The existing redirect guard doesn't help. `#tokenFetch()` takes the origin that may receive the `Authorization` header from the realm URL itself, so the attacker's chosen host counts as same-origin.

The attack is blind, because the token response isn't returned to the attacker. What the attacker gains is the client's network position. For example, from a CI runner the attacker can send requests to hosts they can't route to themselves.

Patches

Fixed in `@sigstore/oci` 0.8.0. By default, registry, token service, redirect, and blob upload requests now require HTTPS and a public network destination. The client blocks loopback, private, link-local, metadata, multicast, reserved, and documentation addresses, and checks every resolved address before it connects.

This changes default behavior. If you use a registry or token service on a private or local address, list its exact origin in `fetchOpts.allowedPrivateOrigins`, or pass `--allow-private-origin` to `sigstore attach`.

Workarounds

The best fix is to upgrade. If you can't upgrade, use `@sigstore/oci` only with registries you trust. In environments such as CI runners, block outbound access from the client to metadata endpoints and internal services.

Details

`#fetchDistributionToken()` in `packages/oci/src/registry.ts` builds the token URL directly from the challenge:

```ts
const authURL = new URL(challenge.realm);
authURL.searchParams.set('service', challenge.service);
authURL.searchParams.set('scope', challenge.scope);

const tokenResponse = await this.#tokenFetch(authURL.toString(), {
headers: { [HEADER_AUTHORIZATION]: `Basic ${basicAuth}` },
}).then(ensureStatus(200));

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
@sigstore/oci< 0.8.0
0.8.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@sigstore/oci
Corregida 0.8.0 -8 d 0.8.0 no afectada
Versiones corregidas0.8.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/sigstore/sigstore-js/security/advisories/GHSA-hrf4-74c9-4hr4

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.