Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/owasp/www-project-csrfguard
The aim of this project is to protect Java applications against CSRF attacks with the use of Synchronizer Tokens
https://github.com/owasp/www-project-csrfguard
csrf csrf-protection hacktoberfest java maven owasp security security-tools
Last synced: 2 days ago
JSON representation
The aim of this project is to protect Java applications against CSRF attacks with the use of Synchronizer Tokens
- Host: GitHub
- URL: https://github.com/owasp/www-project-csrfguard
- Owner: OWASP
- License: bsd-3-clause
- Created: 2019-09-12T20:15:53.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2024-12-09T21:10:44.000Z (14 days ago)
- Last Synced: 2024-12-14T19:02:04.842Z (9 days ago)
- Topics: csrf, csrf-protection, hacktoberfest, java, maven, owasp, security, security-tools
- Language: Java
- Homepage: https://owasp.org/www-project-csrfguard/
- Size: 3.67 MB
- Stars: 83
- Watchers: 14
- Forks: 46
- Open Issues: 9
-
Metadata Files:
- Readme: readme.md
- License: LICENSE
Awesome Lists containing this project
README
# [OWASP CSRFGuard 4.x](https://owasp.org/www-project-csrfguard)
[](https://www.opensource.org/licenses/bsd-license.php)
[](https://github.com/OWASP/www-project-csrfguard/releases)
[](https://search.maven.org/search?q=g:org.owasp%20AND%20a:csrfguard)
[](https://owasp.org/projects#div-flagships)
[](https://github.com/OWASP/www-project-csrfguard/actions/workflows/ci.yaml)
[](https://github.com/OWASP/www-project-csrfguard/actions/workflows/dependency_check.yaml)
[](https://github.com/OWASP/www-project-csrfguard/actions/workflows/snyk.yaml)
## Overview
Welcome to the home of the OWASP CSRFGuard Project! OWASP CSRFGuard is a library that implements a variant of the synchronizer token pattern to mitigate the risk of Cross-Site Request Forgery (CSRF) attacks.
The OWASP CSRFGuard library is integrated through the use of a JavaEE Filter and exposes various automated and manual ways to integrate per-session or pseudo-per-request tokens into HTML. When a user interacts
with this HTML, CSRF prevention tokens (i.e. cryptographically random synchronizer tokens) are submitted with the corresponding HTTP request. It is the responsibility of OWASP CSRFGuard to ensure the token is
present and is valid for the current HTTP request. Any attempt to submit a request to a protected resource without the correct corresponding token is viewed as a CSRF attack in progress and is discarded. Prior
to discarding the request, CSRFGuard can be configured to take one or more actions such as logging aspects of the request and redirecting the user to a landing page. The latest release enhances this strategy to
support the optional verification of HTTP requests submitted using Ajax as well as the optional verification of referrer headers.
## Project Leads
The CSRFGuard project is run by [Azzeddine RAMRAMI](mailto:[email protected]) and [Istvan ALBERT-TOTH](mailto:[email protected]).
## Using with Maven
Add the following dependencies to your Maven POM file to use the library:
**Note**: for the [Jakarta](https://github.com/OWASP/www-project-csrfguard/tree/jakarta) releases use the `-jakarta` suffix in the `version`.
```xml
org.owasp
csrfguard
4.4.0
org.owasp
csrfguard-extension-session
4.4.0
org.owasp
csrfguard-jsp-tags
4.4.0
```
## Building the code
1. Make sure you have [Apache Maven](https://maven.apache.org/) 3.6.3+, JDK 1.8+ and respectively JDK 11+ for Jakarta 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 one of the following commands:
```shell
mvn pre-integration-test -Pdeploy-jsp-webapp -pl csrfguard-test/csrfguard-test-jsp
```
```bash
mvn -Pdeploy-jsp-webapp -pl csrfguard-test/csrfguard-test-jsp tomcat7:run
```
6. Optional: you can use ```mvnDebug``` to enable remote debugging, then connect your IDE to it (default port is 8000)
7. Use a web browser to access ```http://localhost:8080``` to open the home page of the test project
## Uploading to the Maven Central repository (for project leaders)
1. Follow the [Sonatype Open-Source Project Maven Repository Usage Guide](https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide) to create a Sonatype user account;
2. Next, [open a support request](https://issues.sonatype.org/browse/OSSRH) to get your newly created username added to the Maven groupId ```org.owasp```;
3. The ticket must be approved by a CSRFGuard project leader or someone who already has permissions to deploy under the group and artifactId.
4. Once the support request has been completed, follow the instructions in the Sonatype Maven repository usage guide mentioned above to upload new versions to the Maven Central repository.
### GPG Key generation and distribution
See: https://central.sonatype.org/publish/requirements/gpg/
```shell
gpg --full-gen-key
gpg --list-keys
gpg --list-secret-keys # if you've migrated your keys from another machine, make sure you have your secret key(s) imported
gpg --keyserver keys.gnupg.net --send-key # you can define other supported key servers as well
```
### Example `.m2/settings.xml` snippet required for releasing:
```xml
ossrh
ossrh
true
```
Test signing your artifacts manually:
```shell
mvn clean verify -Psign-artifacts -Dgpg.passphrase= # should generate .asc files in the target directory
```
### Deploying to OSS Sonatype / Maven Central
#### Deploy a `-SNAPSHOT` version:
```shell
mvn clean deploy
```
#### Prepare a release:
```shell
mvn release:clean release:prepare
```
1. Set the version number you want to release in <_MAJOR.MINOR.PATCH_> format (e.g. `4.0.0`)
2. Set the SCM release tag: (e.g. `4.0.0`)
3. Set the new development version (e.g. `4.0.1-SNAPSHOT`)
Check the created commits and tag to make sure everything looks as expected:
```shell
git log
git show HEAD
git show HEAD^
git tag -l # list tags
```
#### Rollback the local release:
```shell
mvn release:rollback # or "git reset HEAD^^ --hard"
git tag -d
```
#### Upload the release to OSS Sonatype (staging):
```shell
mvn release:perform
```
The `maven-release-plugin` executes the `deploy` (default). This triggers the execution of the `nexus-staging-maven-plugin`, which uploads the artifacts to the [OSS Sonatype staging repository](https://oss.sonatype.org/#stagingRepositories) and releases them if they meet the requirements.
### [Manual release of a staging repository](https://central.sonatype.org/publish/release/) (in case `autoReleaseAfterClose` is set to `false`)
* Visit https://oss.sonatype.org/#stagingRepositories
* Review the newly created repository against the [requirements](https://central.sonatype.org/publish/requirements/) (JAR files, sources, JavaDocs and associated PGP armored ASCII files are present with the desired version etc.)
* `Close` the repository to trigger the validation of the uploaded components
* If there were no errors, click `Release`
Upon release, the new version is published to the Central Repository, typically within 30 minutes, but updates to [search](https://search.maven.org/) can take up to 4 hours.
#### Push the new release to GitHub:
```shell
git push origin master
git push origin
```
### Maven repositories
You can download pre-compiled versions from:
* [Maven Central repository](https://search.maven.org/search?q=csrfguard)
* [OSS Sonatype Nexus repository](https://oss.sonatype.org/#nexus-search;gav~~csrfguard~~~)