Skip to content

Stroom Authentication/Authorization Bypass when using AWS ALB

Critical
ollie-ncsc published GHSA-x489-xx2m-vc43 Feb 12, 2025

Package

No package listed

Affected versions

>=7.2-beta.53 <7.4.4, 7.5-beta.1

Patched versions

7.2.24, 7.3-beta.22, 7.4.4, 7.5-beta.2

Description

A vulnerability exists that may allow authentication bypass to a Stroom system when configured with ALB and installed in a way that the application is accessible not through the ALB itself. This vulnerability may also allow for SSRF which may lead to code execution or further escalation of privileges when using the AWS metadata URL.

Assumption: Stroom must be configured to use ALB Authentication integration and the application is network accessible.

This vulnerability affects >=7.2-beta.53 and <7.4.4, 7.5-beta.1 This vulnerability has already been fixed (commit #4320 ) so please use versions 7.2.24, 7.3-beta.22, 7.4.4, 7.5-beta.2 or greater.

We would like to thank Liad Eliyahu from Miggo Security for reporting this vulnerability.

Severity

Critical

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
High
Integrity
High
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:H/I:H/A:L

CVE ID

CVE-2025-25182

Weaknesses

Credits