CVE-2025-53099

{"id": "CVE-2025-53099", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.5, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-07-01T15:15:26.277", "references": [{"url": "https://github.com/getsentry/sentry/commit/57f0129e1e977b76fe8d16667a586578791a3dcd", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/commit/ab5fd932ca6bd46529ba3308b4669e3cee719b8f", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/commit/e6241254aead969e6c8490a81cde9a01335df19d", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/pull/85570", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/pull/85571", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/pull/86069", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/pull/86532", "source": "security-advisories@github.com"}, {"url": "https://github.com/getsentry/sentry/security/advisories/GHSA-mgh8-h4xc-pfmj", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-288"}]}], "descriptions": [{"lang": "en", "value": "Sentry is a developer-first error tracking and performance monitoring tool. Prior to version 25.5.0, an attacker with a malicious OAuth application registered with Sentry can take advantage of a race condition and improper handling of authorization code within Sentry to maintain persistence to a user's account. With a specially timed requests and redirect flows, an attacker could generate multiple authorization codes that could be used to exchange for access and refresh tokens. This was possible even after de-authorizing the particular application. This issue has been patched in version 25.5.0. Self-hosted Sentry users should upgrade to version 25.5.0 or higher. Sentry SaaS users do not need to take any action."}, {"lang": "es", "value": "Sentry es una herramienta de seguimiento de errores y monitorizaci\u00f3n del rendimiento centrada en el desarrollador. Antes de la versi\u00f3n 25.5.0, un atacante con una aplicaci\u00f3n OAuth maliciosa registrada en Sentry pod\u00eda aprovechar una condici\u00f3n de ejecuci\u00f3n y la gesti\u00f3n incorrecta del c\u00f3digo de autorizaci\u00f3n en Sentry para mantener la persistencia en la cuenta de un usuario. Con solicitudes y flujos de redirecci\u00f3n con tiempos espec\u00edficos, un atacante pod\u00eda generar m\u00faltiples c\u00f3digos de autorizaci\u00f3n que se pod\u00edan usar para intercambiar tokens de acceso y actualizaci\u00f3n. Esto era posible incluso despu\u00e9s de desautorizar la aplicaci\u00f3n en cuesti\u00f3n. Este problema se ha corregido en la versi\u00f3n 25.5.0. Los usuarios de Sentry autoalojado deben actualizar a la versi\u00f3n 25.5.0 o superior. Los usuarios de Sentry SaaS no necesitan realizar ninguna acci\u00f3n."}], "lastModified": "2025-07-03T15:14:12.767", "sourceIdentifier": "security-advisories@github.com"}