Repository navigation
Document why CSRF stays disabled in the stateless JWT API [skip deploy] #no-deploy - #122
Merged
SebastianLopezO merged 1 commit intoNov 1, 2026
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
SebastianLopezO
force-pushed
the
security/codeql/spring-disabled-csrf-protection
branch
from
November 1, 2026 03:44
35bb5dd to
8666b1f
Compare
SebastianLopezO
deleted the
security/codeql/spring-disabled-csrf-protection
branch
November 1, 2026 03:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Caso
java/spring-disabled-csrf-protectionenSecurityConfiguration.java.es sin estado (
SessionCreationPolicy.STATELESS), solo acepta el JWT en la cabeceraAuthorizationy no usa cookiesni CORS con credenciales (
allowCredentialsno se activa). Un sitio ajeno no puede añadir esa cabecera a una peticióndel navegador de la víctima, así que el ataque no aplica. Activar CSRF obligaría a la PWA a manejar un token extra sin
ganancia de seguridad.
Cambio
día a una cookie, CSRF debe activarse.
Después de fusionar