Stroom Authentication/Authorization Bypass when using AWS ALB

published 2025-02-12 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-4073

cvss: 9.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

Stroom is a data processing, storage and analysis platform. A vulnerability exists starting in version 7.2-beta.53 and prior to versions 7.2.24, 7.3-beta.22, 7.4.4, and 7.5-beta.2 that allows 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 server-side request forgery which may lead to code execution or further privileges escalations when using the AWS metadata URL. This scenario assumes that Stroom must be configured to use ALB Authentication integration and the application is network accessible. The vulnerability has been fixed in versions 7.2.24, 7.3-beta.22, 7.4.4, and 7.5-beta.2.

Patch / fix

fixed in 1 links 1

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

github.com/gchq/stroom#4320 pull request

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 20 mo ago (2025-02-12)

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.4	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Affected products

gchq stroom

Classification

Weakness

CWE-290 Authentication Bypass by Spoofing

References

Sources

CVE List CVE-2025-25182
NVD CVE-2025-25182

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary