CVE-2025-68481

{"id": "CVE-2025-68481", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-68481", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-12-19T20:39:12.855569Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.2, "exploitabilityScore": 1.6}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "fastapi-users", "product": "fastapi-users", "versions": [{"status": "affected", "version": "< 15.0.2"}]}]}], "published": "2025-12-19T21:15:54.823", "references": [{"url": "https://github.com/fastapi-users/fastapi-users/blob/bcee8c9b884de31decb5d799aead3974a0b5b158/fastapi_users/router/oauth.py#L111", "tags": ["Product"], "source": "security-advisories@github.com"}, {"url": "https://github.com/fastapi-users/fastapi-users/blob/bcee8c9b884de31decb5d799aead3974a0b5b158/fastapi_users/router/oauth.py#L57", "tags": ["Product"], "source": "security-advisories@github.com"}, {"url": "https://github.com/fastapi-users/fastapi-users/commit/7cf413cd766b9cb0ab323ce424ddab2c0d235932", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/fastapi-users/fastapi-users/security/advisories/GHSA-5j53-63w8-8625", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-285"}, {"lang": "en", "value": "CWE-352"}]}], "descriptions": [{"lang": "en", "value": "FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \\~1 hour, the victim\u2019s browser will complete the flow. This leads to login CSRF. Depending on the app\u2019s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue."}, {"lang": "es", "value": "FastAPI Users permite a los usuarios a\u00f1adir r\u00e1pidamente un sistema de registro y autenticaci\u00f3n a su proyecto FastAPI. Antes de la versi\u00f3n 15.0.2, los tokens de estado de inicio de sesi\u00f3n de OAuth son completamente sin estado y no llevan entrop\u00eda por solicitud ni ning\u00fan dato que pueda vincularlos a la sesi\u00f3n que inici\u00f3 el flujo de OAuth. 'generate_state_token()' siempre se llama con un diccionario 'state_data' vac\u00edo, por lo que el JWT resultante solo contiene la declaraci\u00f3n de audiencia fija m\u00e1s una marca de tiempo de expiraci\u00f3n. En la devoluci\u00f3n de llamada, la biblioteca simplemente verifica que el JWT se valida bajo 'state_secret' y no ha expirado; no hay ning\u00fan intento de hacer coincidir el valor de estado con el navegador que inici\u00f3 la solicitud de OAuth, ninguna cookie de correlaci\u00f3n y ninguna cach\u00e9 del servidor. Cualquier atacante puede acceder a '/authorize', capturar el estado generado por el servidor, finalizar el flujo de OAuth ascendente con su propia cuenta de proveedor y luego enga\u00f1ar a una v\u00edctima para que cargue '.../callback?code=<attacker_code>&state=<attacker_state>'. Debido a que el JWT de estado es v\u00e1lido para cualquier cliente durante ~1 hora, el navegador de la v\u00edctima completar\u00e1 el flujo. Esto conduce a CSRF de inicio de sesi\u00f3n. Dependiendo de la l\u00f3gica de la aplicaci\u00f3n, el CSRF de inicio de sesi\u00f3n puede llevar a una toma de control de la cuenta de la v\u00edctima o a que el usuario v\u00edctima inicie sesi\u00f3n en la cuenta del atacante. La versi\u00f3n 15.0.2 contiene un parche para el problema."}], "lastModified": "2026-10-13T11:10:00.203", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:fastapi-users_project:fastapi_users:*:*:*:*:*:python:*:*", "vulnerable": true, "matchCriteriaId": "DF422B5A-1DB6-4A93-959D-6D6CA728DCBC", "versionEndExcluding": "15.0.2"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}