Request for digest-bound OpenSSL provenance and backport evidence

Abierto
  • ¿Algo no está bien?
#2,585 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker
Área
devops, security

Línea de trabajo

Start with the specified linux/arm64 image digest and establish its source/build revision and provenance. Then inspect the evaluated Nix derivations, lock inputs, overrides, source hashes, patches, and output identities for each OpenSSL copy, and compare them with the three named advisories. Done means an advisory-by-advisory account of verified fixes, non-applicability, unresolved items, and any replacement digest with provenance.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

documentation

Hello Supabase PostgreSQL maintainers,

Please help establish the OpenSSL patch status of this official linux/arm64 image:

docker.io/supabase/postgres@sha256:2638e94e8e712b2926a2763c37ecfaee4b7abde2cd804a01ac55bba031e52a00

Static inspection identified OpenSSL version-labelled copies:

  • 3.6.0, referenced by PostgreSQL and libpq.
  • 3.0.13, referenced through the legacy pg_net/curl dependency.
  • 3.6.1, referenced by a separate Nix/client dependency closure.

We have not authenticated the applied patches for these exact outputs. Version labels and dependency references alone do not establish vulnerability or exploitability.

Could you provide:

  1. The exact source/build revision bound to this image digest, preferably through verifiable build provenance.
  2. The evaluated Nix derivations, resolved lock inputs, overrides, source hashes and complete applied-patch lists for all three OpenSSL copies.
  3. Trusted output identities—such as signed NAR metadata or equivalent provenance—connecting those derivations to the library outputs included in this image.
  4. The disposition of these independently verified upstream advisories:
    • CVE-2025-15467: CMS AEAD parsing; relevant version ranges include 3.0.13 and 3.6.0.
    • CVE-2026-35189: relative-CRLDP memory allocation; relevant ranges include all three labels.
    • CVE-2026-54875: ARM64/RISC-V SM2 timing/cache leakage; relevant ranges include 3.6.0 and 3.6.1, while 3.0 is explicitly unaffected.
  5. Whether an officially maintained linux/arm64 replacement digest resolves these findings, with corresponding build, dependency and patch provenance.

An advisory-by-advisory response distinguishing applied fixes, documented non-applicability and unresolved items would be helpful.

Thank you.

Lenguaje dominante
Nix
Estrellas
1.8k
Forks
272
Merge medio
4 d 4 h
PR fusionados (30 d)
62

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/postgres

Todos los issues de supabase/postgres

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.