fkie_cve-2025-25182
Vulnerability from fkie_nvd
Published
2025-02-12 17:15
Modified
2025-02-12 17:15
Severity ?
Summary
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.
Impacted products
Vendor Product Version



{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "Stroom es una plataforma de procesamiento, almacenamiento y an\u00e1lisis de datos. Existe una vulnerabilidad a partir de la versi\u00f3n 7.2-beta.53 y anteriores a las versiones 7.2.24, 7.3-beta.22, 7.4.4 y 7.5-beta.2 que permite omitir la autenticaci\u00f3n a Stroom sistema cuando se configura con ALB y se instala de manera que la aplicaci\u00f3n sea accesible sin el ALB en s\u00ed. Esta vulnerabilidad tambi\u00e9n puede permitir Server-Side Request Forgery que puede provocar la ejecuci\u00f3n de c\u00f3digo o mayores escaladas de privilegios al usar la URL de metadatos de AWS. Este escenario supone que Stroom debe configurarse para usar la integraci\u00f3n de autenticaci\u00f3n ALB y que la aplicaci\u00f3n es accesible a trav\u00e9s de la red. La vulnerabilidad se ha corregido en las versiones 7.2.24, 7.3-beta.22, 7.4.4 y 7.5-beta.2."
    }
  ],
  "id": "CVE-2025-25182",
  "lastModified": "2025-02-12T17:15:23.857",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 9.4,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.5,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-02-12T17:15:23.857",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/gchq/stroom/pull/4320"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/gchq/stroom/security/advisories/GHSA-x489-xx2m-vc43"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-290"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…