chore: bump the maven group across 1 directory with 2 updates#12
chore: bump the maven group across 1 directory with 2 updates#12dependabot[bot] wants to merge 3 commits into
Conversation
Bumps the maven group with 2 updates in the / directory: [com.thoughtworks.xstream:xstream](https://github.com/x-stream/xstream) and [org.bitbucket.b_c:jose4j](https://bitbucket.org/b_c/jose4j). Updates `com.thoughtworks.xstream:xstream` from 1.4.5 to 1.4.21 - [Release notes](https://github.com/x-stream/xstream/releases) - [Commits](https://github.com/x-stream/xstream/commits) Updates `org.bitbucket.b_c:jose4j` from 0.9.3 to 0.9.6 - [Commits](https://bitbucket.org/b_c/jose4j/branches/compare/jose4j-0.9.6..jose4j-0.9.3) --- updated-dependencies: - dependency-name: com.thoughtworks.xstream:xstream dependency-version: 1.4.21 dependency-type: direct:production dependency-group: maven - dependency-name: org.bitbucket.b_c:jose4j dependency-version: 0.9.6 dependency-type: direct:production dependency-group: maven ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Copilot review this request please |
There was a problem hiding this comment.
Pull request overview
Updates dependency versions in the root Maven pom.xml to bring two libraries up to more recent releases.
Changes:
- Update
org.bitbucket.b_c:jose4jfrom0.9.3to0.9.6 - Update
com.thoughtworks.xstream:xstreamfrom1.4.5to1.4.21
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <wiremock.version>3.13.1</wiremock.version> | ||
| <xml-resolver.version>1.2</xml-resolver.version> | ||
| <xstream.version>1.4.5</xstream.version> | ||
| <xstream.version>1.4.21</xstream.version> |
There was a problem hiding this comment.
Bumping XStream from 1.4.5 to 1.4.21 may break the “Vulnerable Components” lesson, which explicitly guides users to exploit CVE-2013-7285 via XStream deserialization (see src/main/resources/lessons/vulnerablecomponents/... and GeneralLessonIntegrationTest#vulnerableComponents). Please verify the exploit path still works in the Docker scenario; if not, consider pinning a vulnerable XStream specifically for that lesson (module/profile/shaded dep) or updating the lesson content/tests accordingly. Also note config/dependency-check/project-suppression.xml currently suppresses many XStream CVEs for all versions; after this bump, that suppression may be overly broad and could hide real findings.
| <xstream.version>1.4.21</xstream.version> | |
| <!-- intentionally pinned: the Vulnerable Components lesson and its integration test rely on the historical XStream exploit path --> | |
| <xstream.version>1.4.5</xstream.version> |
….4.21 Agent-Logs-Url: https://github.com/Cluster-Mesh/WebGoat/sessions/cbce017c-d330-4096-b2f0-e028d5794ec3 Co-authored-by: GGuerraReply <133228566+GGuerraReply@users.noreply.github.com>
Agent-Logs-Url: https://github.com/Cluster-Mesh/WebGoat/sessions/cbce017c-d330-4096-b2f0-e028d5794ec3 Co-authored-by: GGuerraReply <133228566+GGuerraReply@users.noreply.github.com>
Reviewed and updated this PR for compatibility with Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Bumps the maven group with 2 updates in the / directory: com.thoughtworks.xstream:xstream and org.bitbucket.b_c:jose4j.
Updates
com.thoughtworks.xstream:xstreamfrom 1.4.5 to 1.4.21Commits
Updates
org.bitbucket.b_c:jose4jfrom 0.9.3 to 0.9.6Commits
1ec20f8[maven-release-plugin] prepare for next development iteratione4da603Update slf4j-api to 1.7.36 to avoid CVE-2018-8088b5720a2Merged in master (pull request #25)72739aefix spelling1afaa1eAdd the PBES2 algorithms to JWE's default blocked AlgorithmConstraints and pu...055225e[maven-release-plugin] prepare release jose4j-0.9.4e2bdbdf[maven-release-plugin] prepare for next development iteration3e97f62Attempt to provide somewhat better error messages for invalid JWTs (especiall...8b2316fJsonWebKey.Factory.newJwk(Key key) to throw an exception when given a private...fa33e98Fix JWKS key resolution for ECDH-ES* decryption with OKP keys (issue #218)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.