Bump csrfguard from 3.0.0 to 4.0.0

[dependabot[bot]]

Bumps csrfguard from 3.0.0 to 4.0.0.

Release notes

Sourced from csrfguard's releases.

OWASP CSRFGuard 4.0.0

Building the code

1. Make sure you have Apache Maven 3.0.4+ and JDK 1.8+ installed
2. Clone this repository locally
3. Build the project by running mvn clean install in the project root directory
4. Build and run the test JSP web application by running mvn pre-integration-test -Pdeploy-jsp-webapp -pl csrfguard-test/csrfguard-test-jsp or mvn -Pdeploy-jsp-webapp -pl csrfguard-test/csrfguard-test-jsp tomcat7:run
5. Optional: you can use mvnDebug to enable remote debugging, then connect your IDE to it (default port is 8000)
6. Use a web browser to access http://localhost:8080 to open the home page of the test project

Using with Maven

OWASP CSRFGuard 4.0.0 is available on the Maven Central repository. Add the following dependencies to your Maven POM file to use the library:

<dependency>
    <groupId>org.owasp</groupId>
    <artifactId>csrfguard</artifactId>
    <version>4.0.0</version>
</dependency>
<!-- Stateful web application support -->
<dependency>
<groupId>org.owasp</groupId>
<artifactId>csrfguard-extension-session</artifactId>
<version>4.0.0</version>
</dependency>
<!-- JSP TAG support -->
<dependency>
<groupId>org.owasp</groupId>
<artifactId>csrfguard-jsp-tags</artifactId>
<version>4.0.0</version>
</dependency>

Release Notes:

• Support for stateless web applications
• Apply "TokenPerPage" approach to AJAX
• Reduced code duplication
• Proper multi-module maven project structure
• The test JSP web application now relies on the latest development JavaScript code
• Improved code quality
• Addressing synchronous XMLHttpRequest deprecation
• Approach changed for master and page token retrieval
• Improved test coverage
• Better solution for looking up page tokens in the JS

... (truncated)

Changelog

Sourced from csrfguard's changelog.

---

title: News layout: null tab: true order: 2 tags: csrfguard

Latest News

We are working on a new version of CSRFGuard including a lot of merge request with good proposals and new code to fix known issues on XSS attacks that bypass CSRFGuard.

Target date for the new release 4.0 : 2021

We need your help. If you want to give few hours of your time please reach out to us.

Commits

• See full diff 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 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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/culturecommunication/ginco/network/alerts).