{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-25182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25182 is a critical authentication bypass vulnerability in gchq stroom, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25182 and fix it if it is affected.\n\nWhat it is: CVE-2025-25182 is a critical authentication bypass vulnerability in gchq stroom, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25182 in the wild and no public exploit code.\n\nAffected product: gchq stroom. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-25182/ (Markdown: https://insights.sbomify.com/CVE-2025-25182/index.md)","id":"CVE-2025-25182","markdown":"https://insights.sbomify.com/CVE-2025-25182/index.md","name":"CVE-2025-25182","record":{"aliases":["GHSA-x489-xx2m-vc43"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Stroom data platform","requires_auth":"none","summary":"Attackers can bypass authentication and potentially execute code via SSRF if Stroom is configured with AWS ALB but accessible directly.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Stroom Authentication/Authorization Bypass when using AWS ALB","id":"CVE-2025-25182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"vLLM using built-in hash() from Python 3.12 leads to predictable hash collisions in vLLM prefix cache","id":"CVE-2025-25183"},"packages":[],"prev":{"headline":"Advantive VeraCore SQL Injection","id":"CVE-2025-25181"},"products":["stroom"],"published":"2025-02-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-12","vendors":["gchq"]},"summary":"Attackers can bypass authentication and potentially execute code via SSRF if Stroom is configured with AWS ALB but accessible directly.","url":"https://insights.sbomify.com/CVE-2025-25182/"}