CVE-2022-23499

{
  "id": "CVE-2022-23499",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2022-23499",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2025-04-23T13:52:30.940928Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "CHANGED",
          "version": "3.1",
          "baseScore": 6.1,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
          "integrityImpact": "LOW",
          "userInteraction": "REQUIRED",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "LOW"
        },
        "impactScore": 2.7,
        "exploitabilityScore": 2.8
      },
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "CHANGED",
          "version": "3.1",
          "baseScore": 6.1,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
          "integrityImpact": "LOW",
          "userInteraction": "REQUIRED",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "LOW"
        },
        "impactScore": 2.7,
        "exploitabilityScore": 2.8
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "TYPO3",
          "product": "html-sanitizer",
          "versions": [
            {
              "status": "affected",
              "version": ">= 1.0.0, < 1.5.0"
            },
            {
              "status": "affected",
              "version": ">= 2.0.0, < 2.1.1"
            }
          ]
        }
      ]
    }
  ],
  "published": "2022-12-13T21:15:11.207",
  "references": [
    {
      "url": "https://github.com/TYPO3/html-sanitizer/security/advisories/GHSA-hvwx-qh2h-xcfj",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/TYPO3/html-sanitizer/security/advisories/GHSA-hvwx-qh2h-xcfj",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-79"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "HTML sanitizer is written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. In versions prior to 1.5.0 or 2.1.1,  malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized due to a parsing issue in the upstream package masterminds/html5. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. The upstream package masterminds/html5 provides HTML raw text elements (`script`, `style`, `noframes`, `noembed` and `iframe`) as DOMText nodes, which were not processed and sanitized further. None of the mentioned elements were defined in the default builder configuration, that's why only custom behaviors, using one of those tag names, were vulnerable to cross-site scripting. This issue has been fixed in versions 1.5.0 and 2.1.1."
    },
    {
      "lang": "es",
      "value": "HTML Sanitizer está escrito en PHP y tiene como objetivo proporcionar un marcado seguro para XSS basado en etiquetas, atributos y valores explícitamente permitidos. En versiones anteriores a 1.5.0 o 2.1.1, el marcado malicioso utilizado en una secuencia con secciones CDATA HTML especiales no se puede filtrar ni sanitizar debido a un problema de análisis en el paquete masterminds/html5. Esto permite evitar el mecanismo de Cross-Site Scripting de typo3/html-sanitizer. El paquete original masterminds/html5 proporciona elementos de texto HTML sin formato (`script`, `style`, `noframes`, `noembed` y `iframe`) como nodos DOMText, que no fueron procesados ni sanitizados más. Ninguno de los elementos mencionados se definió en la configuración predeterminada del generador, es por eso que solo los comportamientos personalizados, que usaban uno de esos nombres de etiquetas, eran vulnerables a las Cross-Site Scripting. Este problema se solucionó en las versiones 1.5.0 y 2.1.1."
    }
  ],
  "lastModified": "2026-06-17T04:30:14.683",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:typo3:html_sanitizer:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "7E6C2A2E-0BD0-4A5F-AACC-35D7628800C1",
              "versionEndIncluding": "1.0.7",
              "versionStartIncluding": "1.0.0"
            },
            {
              "criteria": "cpe:2.3:a:typo3:html_sanitizer:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "D257890D-75AD-4F10-89AF-6C73C43B5298",
              "versionEndExcluding": "2.1.1",
              "versionStartIncluding": "2.0.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}