Skip to content

gosaml2 vulnerable to Denial Of Service Via Deflate Decompression Bomb

Moderate severity GitHub Reviewed Published Mar 1, 2023 in russellhaering/gosaml2 • Updated May 20, 2024

Package

gomod github.com/russellhaering/gosaml2 (Go)

Affected versions

< 0.9.0

Patched versions

0.9.0

Description

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

References

@russellhaering russellhaering published to russellhaering/gosaml2 Mar 1, 2023
Published to the GitHub Advisory Database Mar 2, 2023
Reviewed Mar 2, 2023
Published by the National Vulnerability Database Mar 3, 2023
Last updated May 20, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

0.121%
(48th percentile)

Weaknesses

CVE ID

CVE-2023-26483

GHSA ID

GHSA-6gc3-crp7-25w5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.