ghsa-hfj7-542q-8fvv
Vulnerability from github
Published
2025-07-17 19:40
Modified
2025-07-17 19:40
Severity ?
4.7 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Summary
DiracX-Web is vulnerable to attack through an Open Redirect on its login page
Details

Summary

An attacker can forge a request to redirect an authenticated user to any arbitrary website.

Details

On the login page, we have a redirect field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI.

Paired with a parameter pollution, we can hide our malicious URI (ex: https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb).

PoC

https://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern.ch/auth

This POC can leak user's position.

Impact

This could be used for phishing and extracting new data (such as redirecting to a new "log in" page, and asking users to reenter credentials).

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@dirac-grid/diracx-web-components"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.1.0-a8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-54066"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-601"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-07-17T19:40:59Z",
    "nvd_published_at": "2025-07-17T15:15:27Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\n\nAn attacker can forge a request to redirect an authenticated user to any arbitrary website.\n\n### Details\n\nOn the login page, we have a `redirect` field which is the location where the server will redirect the user. This URI is not verified, and can be an arbitrary URI.\n\nPaired with a parameter pollution, we can hide our malicious URI (ex: `https://dns.com/?param1=im_hidden_if_theres_lot_of_args?param1=bbb`).\n\n### PoC\n\nhttps://diracx-cert.app.cern.ch/auth?redirect=https://ipcim.com/en/where/?dsdsd=qsqsfsjfnsfniizaeiaapzqlalkqkaizqqijsjaopmqmxna?redirect=https://diracx-cert-app.cern.ch/auth\n\nThis POC can leak user\u0027s position.\n\n### Impact\n\nThis could be used for phishing and extracting new data (such as redirecting to a new \"log in\" page, and asking users to reenter credentials).",
  "id": "GHSA-hfj7-542q-8fvv",
  "modified": "2025-07-17T19:40:59Z",
  "published": "2025-07-17T19:40:59Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/DIRACGrid/diracx-web/security/advisories/GHSA-hfj7-542q-8fvv"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54066"
    },
    {
      "type": "WEB",
      "url": "https://github.com/DIRACGrid/diracx-web/commit/eba3b7bc4f9d394074215986e6d3c15b546b25d5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/DIRACGrid/diracx-web"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "DiracX-Web is vulnerable to attack through an Open Redirect on its login page"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.