Vulnérabilités / CVE-2026-73080

critique

CVE-2026-73080

SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle

Publiée Modifiée CWE 918
Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par source

GHSA9.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Bitnami9.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Le label propre à Trivy est CRITICAL. Critique selon GHSA, Bitnami.

Description

SeaweedFS is a distributed storage system. Prior to 4.24, VolumeServer.FetchAndWriteNeedle in weed/server/volume_grpc_remote.go fetches a caller-supplied remote endpoint through weed/remote_storage/s3/s3_storage_client.go and writes the response into a needle. The RPC performs no authentication and no target validation, allowing anyone who can reach a volume server's gRPC port to cause requests to arbitrary hosts, including loopback, link-local, RFC 1918, and cloud metadata endpoints such as 169.254.169.254, and read the response. On cloud deployments, this can disclose instance metadata and IAM credentials and reach otherwise unexposed internal services. The volume server gRPC plane is unauthenticated by default, and configuring documented JWT signing keys does not protect this RPC. This issue is fixed in version 4.24.

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
bitnami::Bitnami Vulnerability Databaseseaweedfs4.24.0
go::GitHub Security Advisory Gogithub.com/seaweedfs/seaweedfs0.0.0-20260512171120-69da20bdaec9
minimosseaweedfs-cosi-driver, seaweedfs-cosi-driver-fips0.3.1-r6
Afficher les 4 entrées de 3 sources
SourcePaquetCorrigé en
bitnami::Bitnami Vulnerability Databaseseaweedfs4.24.0
go::GitHub Security Advisory Gogithub.com/seaweedfs/seaweedfs0.0.0-20260512171120-69da20bdaec9
minimosseaweedfs-cosi-driver0.3.1-r6
minimosseaweedfs-cosi-driver-fips0.3.1-r6

Références

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.