« Volver al listado

CVE-2025-47781

Estado: AnalizadaCrítica (9.8)—

Rallly is an open-source scheduling and collaboration tool. Versions up to and including 3.22.1 of the application features token based authentication. When a user attempts to login to the application, they insert their email and a 6 digit code is sent to their email address to complete the authentication.

Leer descripción completaMostrar menos

A token that consists of 6 digits only presents weak entropy however and when coupled with no token brute force protection, makes it possible for an unauthenticated attacker with knowledge of a valid email address to successfully brute force the token within 15 minutes (token expiration time) and take over the account associated with the targeted email address. All users on the Rallly applications are impacted. As long as an attacker knows the user's email address they used to register on the app, they can systematically take over any user account. For the authentication mechanism to be safe, the token would need to be assigned a complex high entropy value that cannot be bruteforced within reasonable time, and ideally rate limiting the /api/auth/callback/email endpoint to further make brute force attempts unreasonable within the 15 minutes time. As of time of publication, no patched versions are available.

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

AV:N/PR:N/UI:N permite ataque remoto no autenticado. Token de 6 dígitos sin protección contra fuerza bruta permite tomar control de cuentas válidas (T1078.001) y potencialmente modificar configuración de autenticación (T1556.001).

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Vulnerability ScanningPrivileged Account ManagementPassword PoliciesNetwork SegmentationMulti-factor AuthenticationLimit Access to Resource Over Network

Tecnologías afectadas (1)

Rallly — Rallly

CWE

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2025-47781",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-47781",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-05-14T17:37:06.796122Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 9.8,
          "attackVector": "NETWORK",
          "baseSeverity": "CRITICAL",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "lukevella",
          "product": "rallly",
          "versions": [
            {
              "status": "affected",
              "version": "<= 3.11.2"
            }
          ]
        }
      ]
    }
  ],
  "published": "2025-05-14T16:15:29.257",
  "references": [
    {
      "url": "https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-331"
        }
      ]
    },
    {
      "type": "Primary",
      "source": "nvd@nist.gov",
      "description": [
        {
          "lang": "en",
          "value": "CWE-331"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Rallly is an open-source scheduling and collaboration tool. Versions up to and including 3.22.1 of the application features token based authentication. When a user attempts to login to the application, they insert their email and a 6 digit code is sent to their email address to complete the authentication. A token that consists of 6 digits only presents weak entropy however and when coupled with no token brute force protection, makes it possible for an unauthenticated attacker with knowledge of a valid email address to successfully brute force the token within 15 minutes (token expiration time) and take over the account associated with the targeted email address. All users on the Rallly applications are impacted. As long as an attacker knows the user's email address they used to register on the app, they can systematically take over any user account. For the authentication mechanism to be safe, the token would need to be assigned a complex high entropy value that cannot be bruteforced within reasonable time, and ideally rate limiting the /api/auth/callback/email endpoint to further make brute force attempts unreasonable within the 15 minutes time. As of time of publication, no patched versions are available."
    },
    {
      "lang": "es",
      "value": "Rallly es una herramienta de código abierto para la programación y la colaboración. Las versiones de la aplicación, hasta la 3.22.1 (incluida), incorporan autenticación mediante token. Cuando un usuario intenta iniciar sesión, introduce su correo electrónico y se le envía un código de 6 dígitos para completar la autenticación. Sin embargo, un token de 6 dígitos presenta una entropía débil y, al no contar con protección contra ataques de fuerza bruta, permite que un atacante no autenticado, con conocimiento de una dirección de correo electrónico válida, ataque el token por fuerza bruta en 15 minutos (fecha de caducidad) y se apodere de la cuenta asociada a dicha dirección. Todos los usuarios de las aplicaciones de Rallly se ven afectados. Si un atacante conoce la dirección de correo electrónico del usuario que se registró en la aplicación, puede apropiarse sistemáticamente de cualquier cuenta. Para que el mecanismo de autenticación sea seguro, se debe asignar al token un valor complejo de alta entropía que no pueda ser atacado por fuerza bruta en un tiempo razonable. Idealmente, se debe limitar la velocidad del endpoint /api/auth/callback/email para que los intentos de fuerza bruta sean aún más irrazonables dentro de los 15 minutos. Al momento de la publicación, no hay versiones parcheadas disponibles."
    }
  ],
  "lastModified": "2026-06-17T09:28:40.843",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:rallly:rallly:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "67827911-8578-47EF-A968-382909B02267",
              "versionEndIncluding": "3.11.2"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}