gosaml2 vulnerable to Denial Of Service Via Deflate Decompression Bomb

TRUNG BÌNH 5.3CVE-2023-26483 · GHSA-6gc3-crp7-25w5 · GO-2023-1602 · Công bố 03/03/2023 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2023-26483 là lỗ hổng mức TRUNG BÌNH (CVSS 5.3) ảnh hưởng github.com/russellhaering/gosaml2, gosaml2 (gosaml2 project).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.96%, cao hơn 61.7% các lỗ hổng khác.
Cách xử lý: cập nhật lên 0.9.0 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
github.com/russellhaering/gosaml2 Go	`< 0.9.0`	`0.9.0`
gosaml2 gosaml2_project	`< 0.9.0`	`0.9.0`

Mô tả

Impact

SAML Service Providers using this library for SAML authentication support are likely susceptible to Denial of Service attacks. A bug in this library enables attackers to craft a deflate-compressed request which will consume significantly more memory during processing than the size of the original request. This may eventually lead to memory exhaustion and the process being killed.

Mitigation

The maximum compression ratio achievable with deflate is 1032:1, so by limiting the size of bodies passed to gosaml2, limiting the rate and concurrency of calls, and ensuring that lots of memory is available to the process it may be possible to help Go's garbage collector "keep up".

Implementors are encouraged not to rely on this.

Patches

This issue is addressed in v0.9.0

Mô tả của NVD

gosaml2 is a Pure Go implementation of SAML 2.0. SAML Service Providers using this library for SAML authentication support are likely susceptible to Denial of Service attacks. A bug in this library enables attackers to craft a `deflate`-compressed request which will consume significantly more memory during processing than the size of the original request. This may eventually lead to memory exhaustion and the process being killed. The maximum compression ratio achievable with `deflate` is 1032:1, so by limiting the size of bodies passed to gosaml2, limiting the rate and concurrency of calls, and ensuring that lots of memory is available to the process it _may_ be possible to help Go's garbage collector "keep up". Implementors are encouraged not to rely on this. This issue is fixed in version 0.9.0.