Request for digest-bound OpenSSL provenance and backport evidence

未关闭
#2,585 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker
领域
devops, security

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Nix
星标
1.8k
派生
272
平均合并
4 天 4 小时
30 天内合并 PR
62

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

supabase/postgres 的其他 Issue

查看 supabase/postgres 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。