FKIE_CVE-2025-47781
Vulnerability from fkie_nvd - Published: 2025-05-14 16:15 - Updated: 2026-06-17 09:28| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv | Exploit, Vendor Advisory | |
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv | Exploit, Vendor Advisory |
{
"affected": [
{
"affectedData": [
{
"product": "rallly",
"vendor": "lukevella",
"versions": [
{
"status": "affected",
"version": "\u003c= 3.11.2"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:rallly:rallly:*:*:*:*:*:*:*:*",
"matchCriteriaId": "67827911-8578-47EF-A968-382909B02267",
"versionEndIncluding": "3.11.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"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\u0027s 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\u00f3digo abierto para la programaci\u00f3n y la colaboraci\u00f3n. Las versiones de la aplicaci\u00f3n, hasta la 3.22.1 (incluida), incorporan autenticaci\u00f3n mediante token. Cuando un usuario intenta iniciar sesi\u00f3n, introduce su correo electr\u00f3nico y se le env\u00eda un c\u00f3digo de 6 d\u00edgitos para completar la autenticaci\u00f3n. Sin embargo, un token de 6 d\u00edgitos presenta una entrop\u00eda d\u00e9bil y, al no contar con protecci\u00f3n contra ataques de fuerza bruta, permite que un atacante no autenticado, con conocimiento de una direcci\u00f3n de correo electr\u00f3nico v\u00e1lida, ataque el token por fuerza bruta en 15 minutos (fecha de caducidad) y se apodere de la cuenta asociada a dicha direcci\u00f3n. Todos los usuarios de las aplicaciones de Rallly se ven afectados. Si un atacante conoce la direcci\u00f3n de correo electr\u00f3nico del usuario que se registr\u00f3 en la aplicaci\u00f3n, puede apropiarse sistem\u00e1ticamente de cualquier cuenta. Para que el mecanismo de autenticaci\u00f3n sea seguro, se debe asignar al token un valor complejo de alta entrop\u00eda 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\u00fan m\u00e1s irrazonables dentro de los 15 minutos. Al momento de la publicaci\u00f3n, no hay versiones parcheadas disponibles."
}
],
"id": "CVE-2025-47781",
"lastModified": "2026-06-17T09:28:40.843",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"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:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-47781",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-05-14T17:37:06.796122Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-05-14T16:15:29.257",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/lukevella/rallly/security/advisories/GHSA-gm8g-3r3j-48hv"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-331"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-331"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.