Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

build(deps): bump ckeditor5 and @ckeditor/ckeditor5-build-classic #2297

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

build(deps): bump ckeditor5 and @ckeditor/ckeditor5-build-classic #2297

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 25, 2024

Bumps ckeditor5 to 43.1.1 and updates ancestor dependency @ckeditor/ckeditor5-build-classic. These dependencies need to be updated together.

Updates ckeditor5 from 40.0.0 to 43.1.1

Release notes

Sourced from ckeditor5's releases.

v43.1.1

We are happy to announce the release of CKEditor 5 v43.1.1.

During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package (CVE-2024-45613). This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert malicious content into the editor, which might happen with a very specific editor configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

  1. The Block Toolbar plugin is enabled.
  2. One of the following plugins is also enabled:

You can read more details in the relevant security advisory and contact us if you have more questions.

Taking the occasion, we decided to introduce additional hardening to some parts of our codebase that introduce theoretical and unexploitable issues. Our security team confirmed that none of these issues were exploitable in a real scenario, however, we decided to fix them, in order to increase the overall security posture of our software.

Released packages

Check out the Versioning policy guide for more information.

Other releases:

... (truncated)

Changelog

Sourced from ckeditor5's changelog.

43.1.1 (September 25, 2024)

We are happy to announce the release of CKEditor 5 v43.1.1.

During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package (CVE-2024-45613). This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert malicious content into the editor, which might happen with a very specific editor configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

  1. The Block Toolbar plugin is enabled.
  2. One of the following plugins is also enabled:

You can read more details in the relevant security advisory and contact us if you have more questions.

Taking the occasion, we decided to introduce additional hardening to some parts of our codebase that introduce theoretical and unexploitable issues. Our security team confirmed that none of these issues were exploitable in a real scenario, however, we decided to fix them, in order to increase the overall security posture of our software.

Released packages

Check out the Versioning policy guide for more information.

Other releases:

... (truncated)

Commits
  • 6b1e550 Release: v43.1.1.
  • e63d992 Merge pull request #17148 from ckeditor/release_to_release
  • 2c43f71 Merge pull request #17113 from ckeditor/ck/fix-selection-hang-test
  • 9c2d297 Changelog for v43.1.1.
  • 84cdd9c Release: v43.1.0.
  • b32ee03 Merge pull request #17034 from ckeditor/revert-16878-ci/16870-sanitize-html
  • de4a416 Docs: minor fix. [skip ci]
  • 1eff562 Updated CHANGELOG.md. [short flow]
  • b2021fa Update docs/updating/update-to-43.md
  • aeafee9 Update docs/updating/update-to-43.md
  • Additional commits viewable in compare view

Updates @ckeditor/ckeditor5-build-classic from 40.0.0 to 43.1.1

Release notes

Sourced from @​ckeditor/ckeditor5-build-classic's releases.

v43.1.1

We are happy to announce the release of CKEditor 5 v43.1.1.

During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package (CVE-2024-45613). This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert malicious content into the editor, which might happen with a very specific editor configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

  1. The Block Toolbar plugin is enabled.
  2. One of the following plugins is also enabled:

You can read more details in the relevant security advisory and contact us if you have more questions.

Taking the occasion, we decided to introduce additional hardening to some parts of our codebase that introduce theoretical and unexploitable issues. Our security team confirmed that none of these issues were exploitable in a real scenario, however, we decided to fix them, in order to increase the overall security posture of our software.

Released packages

Check out the Versioning policy guide for more information.

Other releases:

... (truncated)

Changelog

Sourced from @​ckeditor/ckeditor5-build-classic's changelog.

43.1.1 (September 25, 2024)

We are happy to announce the release of CKEditor 5 v43.1.1.

During a recent internal audit, we identified a Cross-Site Scripting (XSS) vulnerability in the CKEditor 5 clipboard package (CVE-2024-45613). This vulnerability could be triggered by a specific user action, leading to unauthorized JavaScript code execution, if the attacker managed to insert malicious content into the editor, which might happen with a very specific editor configuration.

This vulnerability affects only installations where the editor configuration meets the following criteria:

  1. The Block Toolbar plugin is enabled.
  2. One of the following plugins is also enabled:

You can read more details in the relevant security advisory and contact us if you have more questions.

Taking the occasion, we decided to introduce additional hardening to some parts of our codebase that introduce theoretical and unexploitable issues. Our security team confirmed that none of these issues were exploitable in a real scenario, however, we decided to fix them, in order to increase the overall security posture of our software.

Released packages

Check out the Versioning policy guide for more information.

Other releases:

... (truncated)

Commits
  • 6b1e550 Release: v43.1.1.
  • 84cdd9c Release: v43.1.0.
  • fe96879 Internal (build-*): Builds. [skip ci]
  • 5804ae9 Internal (build-*): Builds.
  • a0ac4f4 Release: v43.0.0.
  • 739f712 Internal (build-*): Builds.
  • fc38c1b Internal (build-*): Builds.
  • e1037ef Internal (build-*): Builds.
  • 6ecf5f7 Internal (build-*): Builds.
  • f0e0db6 Changed global name for ckeditor5 for umd build and bump ckeditor5-dev-* to t...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
build(deps): bump ckeditor5 and @ckeditor/ckeditor5-build-classic
0f08d19 
Bumps [ckeditor5](https://github.com/ckeditor/ckeditor5) to 43.1.1 and updates ancestor dependency [@ckeditor/ckeditor5-build-classic](https://github.com/ckeditor/ckeditor5/tree/HEAD/packages/ckeditor5-build-classic). These dependencies need to be updated together.


Updates `ckeditor5` from 40.0.0 to 43.1.1
- [Release notes](https://github.com/ckeditor/ckeditor5/releases)
- [Changelog](https://github.com/ckeditor/ckeditor5/blob/master/CHANGELOG.md)
- [Commits](ckeditor/ckeditor5@v40.0.0...v43.1.1)

Updates `@ckeditor/ckeditor5-build-classic` from 40.0.0 to 43.1.1
- [Release notes](https://github.com/ckeditor/ckeditor5/releases)
- [Changelog](https://github.com/ckeditor/ckeditor5/blob/master/CHANGELOG.md)
- [Commits](https://github.com/ckeditor/ckeditor5/commits/v43.1.1/packages/ckeditor5-build-classic)

---
updated-dependencies:
- dependency-name: ckeditor5
  dependency-type: indirect
- dependency-name: "@ckeditor/ckeditor5-build-classic"
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants