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.

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

[Security] Bump synapse.version from 2.1.7-wso2v183 to 3.0.1 #119

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

@dependabot-preview dependabot-preview bot commented Nov 4, 2020

Bumps synapse.version from 2.1.7-wso2v183 to 3.0.1.
Updates synapse-core from 2.1.7-wso2v183 to 3.0.1 This update includes a security fix.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Remote Code Execution in Apache Synapse In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.

Affected versions: < 3.0.1


Updates synapse-extensions from 2.1.7-wso2v183 to 3.0.1

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 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)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added dependencies Pull requests that update a dependency file security Pull requests that address a security vulnerability labels Nov 4, 2020
@dependabot-preview
Copy link
Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@dependabot-preview dependabot-preview bot force-pushed the dependabot/maven/synapse.version-3.0.1 branch from 9a4adba to 29d41d6 Compare April 2, 2021 16:57
@dependabot-preview dependabot-preview bot force-pushed the dependabot/maven/synapse.version-3.0.1 branch from 29d41d6 to 343eff3 Compare April 5, 2021 06:32
@dependabot-preview dependabot-preview bot force-pushed the dependabot/maven/synapse.version-3.0.1 branch from 343eff3 to 6b6fec1 Compare April 7, 2021 01:53
@dependabot-preview dependabot-preview bot force-pushed the dependabot/maven/synapse.version-3.0.1 branch from 6b6fec1 to 409e11a Compare April 12, 2021 17:09
tharikaGitHub and others added 3 commits April 16, 2021 06:07
Bumps `synapse.version` from 2.1.7-wso2v183 to 3.0.1.

Updates `synapse-core` from 2.1.7-wso2v183 to 3.0.1

Updates `synapse-extensions` from 2.1.7-wso2v183 to 3.0.1

Signed-off-by: dependabot-preview[bot] <[email protected]>
@dependabot-preview dependabot-preview bot force-pushed the dependabot/maven/synapse.version-3.0.1 branch from 409e11a to 3a62972 Compare April 16, 2021 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file security Pull requests that address a security vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant