gchq stroom up to 7.2.23/7.3-beta.21/7.4.3/7.5-beta.1 authentication spoofing

Summaryinfo

A vulnerability, which was classified as critical, has been found in gchq stroom up to 7.2.23/7.3-beta.21/7.4.3/7.5-beta.1. Affected is an unknown function. Performing a manipulation results in authentication spoofing. This vulnerability is cataloged as CVE-2025-25182. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in gchq stroom up to 7.2.23/7.3-beta.21/7.4.3/7.5-beta.1. This affects an unknown functionality. The manipulation with an unknown input leads to a authentication spoofing vulnerability. CWE is classifying the issue as CWE-290. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-25182 since 02/03/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 7.2.24, 7.3-beta.22, 7.4.4 or 7.5-beta.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• gchq

Name

• stroom

Version

• 7.2.0
• 7.2.1
• 7.2.2
• 7.2.3
• 7.2.4
• 7.2.5
• 7.2.6
• 7.2.7
• 7.2.8
• 7.2.9
• 7.2.10
• 7.2.11
• 7.2.12
• 7.2.13
• 7.2.14
• 7.2.15
• 7.2.16
• 7.2.17
• 7.2.18
• 7.2.19
• 7.2.20
• 7.2.21
• 7.2.22
• 7.2.23
• 7.3-beta.0
• 7.3-beta.1
• 7.3-beta.2
• 7.3-beta.3
• 7.3-beta.4
• 7.3-beta.5
• 7.3-beta.6
• 7.3-beta.7
• 7.3-beta.8
• 7.3-beta.9
• 7.3-beta.10
• 7.3-beta.11
• 7.3-beta.12
• 7.3-beta.13
• 7.3-beta.14
• 7.3-beta.15
• 7.3-beta.16
• 7.3-beta.17
• 7.3-beta.18
• 7.3-beta.19
• 7.3-beta.20
• 7.3-beta.21
• 7.4.0
• 7.4.1
• 7.4.2
• 7.4.3
• 7.5-beta.0
• 7.5-beta.1

Website

• Product: https://github.com/gchq/stroom/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion