CVE-2023-39531

{
  "id": "CVE-2023-39531",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2023-39531",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2024-10-03T15:12:07.030429Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "CHANGED",
          "version": "3.1",
          "baseScore": 6.5,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N",
          "integrityImpact": "LOW",
          "userInteraction": "REQUIRED",
          "attackComplexity": "HIGH",
          "availabilityImpact": "NONE",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 4.7,
        "exploitabilityScore": 1.3
      },
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 6.8,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "HIGH",
          "availabilityImpact": "NONE",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.2,
        "exploitabilityScore": 1.6
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "getsentry",
          "product": "sentry",
          "versions": [
            {
              "status": "affected",
              "version": ">= 10.0.0, < 23.7.2"
            }
          ]
        }
      ]
    }
  ],
  "published": "2023-08-09T17:15:09.827",
  "references": [
    {
      "url": "https://github.com/getsentry/sentry/security/advisories/GHSA-hgj4-h2x3-rfx4",
      "tags": [
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/getsentry/sentry/security/advisories/GHSA-hgj4-h2x3-rfx4",
      "tags": [
        "Vendor Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-287"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 23.7.2, an attacker with sufficient client-side exploits could retrieve a valid access token for another user during the OAuth token exchange due to incorrect credential validation. The client ID must be known and the API application must have already been authorized on the targeted user account. Sentry SaaS customers do not need to take any action. Self-hosted installations should upgrade to version 23.7.2 or higher. There are no direct workarounds, but users should review applications authorized on their account and remove any that are no longer needed.\n\n"
    },
    {
      "lang": "es",
      "value": "Sentry es una plataforma de seguimiento de errores y monitorización del rendimiento. A partir de la versión 10.0.0 y antes de la versión 23.7.2, un atacante con suficientes exploits del lado del cliente podría recuperar un token de acceso válido para otro usuario durante el intercambio de tokens OAuth debido a una validación de credenciales incorrecta. El ID del cliente debe ser conocido y la aplicación API debe haber sido ya autorizada en la cuenta del usuario objetivo. Los clientes de Sentry SaaS no necesitan realizar ninguna acción. Las instalaciones autoalojadas deben actualizarse a la versión 23.7.2 o superior. No hay soluciones directas, pero los usuarios deben revisar las aplicaciones autorizadas en su cuenta y eliminar las que ya no sean necesarias."
    }
  ],
  "lastModified": "2026-06-17T06:12:31.983",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:sentry:sentry:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "F9FF2EA1-64DB-404A-A036-C2E4983773CB",
              "versionEndExcluding": "23.7.2",
              "versionStartIncluding": "10.0.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}