gsd-2022-31175
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5's packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `<textarea>` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.
Aliases
Aliases



{
  "GSD": {
    "alias": "CVE-2022-31175",
    "description": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.",
    "id": "GSD-2022-31175"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2022-31175"
      ],
      "details": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.",
      "id": "GSD-2022-31175",
      "modified": "2023-12-13T01:19:17.899687Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "security-advisories@github.com",
        "ID": "CVE-2022-31175",
        "STATE": "PUBLIC",
        "TITLE": "Cross-site scripting caused by the editor instance destroying process in ckeditor5"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "ckeditor5",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "\u003c 35.0.1"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "ckeditor"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue."
          }
        ]
      },
      "impact": {
        "cvss": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 5.8,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L",
          "version": "3.1"
        }
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "CWE-79: Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j",
            "refsource": "CONFIRM",
            "url": "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j"
          },
          {
            "name": "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html",
            "refsource": "MISC",
            "url": "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html"
          },
          {
            "name": "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html",
            "refsource": "MISC",
            "url": "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html"
          },
          {
            "name": "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html",
            "refsource": "MISC",
            "url": "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html"
          }
        ]
      },
      "source": {
        "advisory": "GHSA-42wq-rch8-6f6j",
        "discovery": "UNKNOWN"
      }
    },
    "gitlab.com": {
      "advisories": [
        {
          "affected_range": "\u003c35.0.1",
          "affected_versions": "All versions before 35.0.1",
          "cwe_ids": [
            "CWE-1035",
            "CWE-79",
            "CWE-937"
          ],
          "date": "2022-08-06",
          "description": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.",
          "fixed_versions": [
            "35.0.1"
          ],
          "identifier": "CVE-2022-31175",
          "identifiers": [
            "GHSA-42wq-rch8-6f6j",
            "CVE-2022-31175"
          ],
          "not_impacted": "All versions starting from 35.0.1",
          "package_slug": "npm/@ckeditor/ckeditor5-html-embed",
          "pubdate": "2022-08-06",
          "solution": "Upgrade to version 35.0.1 or above.",
          "title": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)",
          "urls": [
            "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j",
            "https://nvd.nist.gov/vuln/detail/CVE-2022-31175",
            "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html",
            "https://github.com/advisories/GHSA-42wq-rch8-6f6j"
          ],
          "uuid": "28f9e6ad-9f29-435a-9a3a-6624ed80b3ce"
        },
        {
          "affected_range": "\u003c35.0.1",
          "affected_versions": "All versions before 35.0.1",
          "cwe_ids": [
            "CWE-1035",
            "CWE-79",
            "CWE-937"
          ],
          "date": "2022-08-06",
          "description": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.",
          "fixed_versions": [
            "35.0.1"
          ],
          "identifier": "CVE-2022-31175",
          "identifiers": [
            "GHSA-42wq-rch8-6f6j",
            "CVE-2022-31175"
          ],
          "not_impacted": "All versions starting from 35.0.1",
          "package_slug": "npm/@ckeditor/ckeditor5-html-support",
          "pubdate": "2022-08-06",
          "solution": "Upgrade to version 35.0.1 or above.",
          "title": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)",
          "urls": [
            "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j",
            "https://nvd.nist.gov/vuln/detail/CVE-2022-31175",
            "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html",
            "https://github.com/advisories/GHSA-42wq-rch8-6f6j"
          ],
          "uuid": "09754e0e-91d6-4a21-9870-8fe8c5e257d2"
        },
        {
          "affected_range": "\u003c35.0.1",
          "affected_versions": "All versions before 35.0.1",
          "cvss_v3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N",
          "cwe_ids": [
            "CWE-1035",
            "CWE-79",
            "CWE-937"
          ],
          "date": "2022-08-09",
          "description": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue.",
          "fixed_versions": [
            "35.0.1"
          ],
          "identifier": "CVE-2022-31175",
          "identifiers": [
            "CVE-2022-31175",
            "GHSA-42wq-rch8-6f6j"
          ],
          "not_impacted": "All versions starting from 35.0.1",
          "package_slug": "npm/@ckeditor/ckeditor5-markdown-gfm",
          "pubdate": "2022-08-03",
          "solution": "Upgrade to version 35.0.1 or above.",
          "title": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)",
          "urls": [
            "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j",
            "https://nvd.nist.gov/vuln/detail/CVE-2022-31175",
            "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html",
            "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html",
            "https://github.com/advisories/GHSA-42wq-rch8-6f6j"
          ],
          "uuid": "452eb304-3134-4f4f-987b-28f9a9c9cca9"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:ckeditor:ckeditor5-html-support:*:*:*:*:*:node.js:*:*",
                "cpe_name": [],
                "versionEndExcluding": "35.0.1",
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:ckeditor:ckeditor5-html-embed:*:*:*:*:*:node.js:*:*",
                "cpe_name": [],
                "versionEndExcluding": "35.0.1",
                "vulnerable": true
              },
              {
                "cpe23Uri": "cpe:2.3:a:ckeditor:ckeditor5-markdown-gfm:*:*:*:*:*:node.js:*:*",
                "cpe_name": [],
                "versionEndExcluding": "35.0.1",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "security-advisories@github.com",
          "ID": "CVE-2022-31175"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "CKEditor 5 is a JavaScript rich text editor. A cross-site scripting vulnerability has been discovered affecting three optional CKEditor 5\u0027s packages in versions prior to 35.0.1. The vulnerability allowed to trigger a JavaScript code after fulfilling special conditions. The affected packages are `@ckeditor/ckeditor5-markdown-gfm`, `@ckeditor/ckeditor5-html-support`, and `@ckeditor/ckeditor5-html-embed`. The specific conditions are 1) Using one of the affected packages. In case of `ckeditor5-html-support` and `ckeditor5-html-embed`, additionally, it was required to use a configuration that allows unsafe markup inside the editor. 2) Destroying the editor instance and 3) Initializing the editor on an element and using an element other than `\u003ctextarea\u003e` as a base. The root cause of the issue was a mechanism responsible for updating the source element with the markup coming from the CKEditor 5 data pipeline after destroying the editor. This vulnerability might affect a small percent of integrators that depend on dynamic editor initialization/destroy and use Markdown, General HTML Support or HTML embed features. The problem has been recognized and patched. The fix is available in version 35.0.1. There are no known workarounds for this issue."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-79"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j",
              "refsource": "CONFIRM",
              "tags": [
                "Third Party Advisory"
              ],
              "url": "https://github.com/ckeditor/ckeditor5/security/advisories/GHSA-42wq-rch8-6f6j"
            },
            {
              "name": "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html",
              "refsource": "MISC",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html"
            },
            {
              "name": "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html",
              "refsource": "MISC",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://ckeditor.com/docs/ckeditor5/latest/features/html-embed.html"
            },
            {
              "name": "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html",
              "refsource": "MISC",
              "tags": [
                "Vendor Advisory"
              ],
              "url": "https://ckeditor.com/docs/ckeditor5/latest/features/general-html-support.html"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N",
            "version": "3.1"
          },
          "exploitabilityScore": 1.6,
          "impactScore": 2.7
        }
      },
      "lastModifiedDate": "2022-08-09T17:28Z",
      "publishedDate": "2022-08-03T19:15Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…