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

CVE-2016-5007 @ Maven-org.springframework.security:spring-security-config-3.2.4.RELEASE #91

Open
amitshalemCx opened this issue Aug 10, 2022 · 0 comments

Comments

@amitshalemCx
Copy link
Owner

amitshalemCx commented Aug 10, 2022

Vulnerable Package issue exists @ Maven-org.springframework.security:spring-security-config-3.2.4.RELEASE in branch main

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.

Namespace: amitshalemCx
Repository: ast-advanced-lab
Repository Url: https://github.com/amitshalemCx/ast-advanced-lab
CxAST-Project: amitshalemCx/ast-advanced-lab
CxAST platform scan: e4664af5-6704-4007-97f2-d490d09af097
Branch: main
Application: ast-advanced-lab
Severity: HIGH
State: NOT_IGNORED
Status: RECURRENT
CWE: CWE-264


Additional Info
Attack vector: NETWORK
Attack complexity: LOW
Confidentiality impact: NONE
Availability impact: NONE
Remediation Upgrade Recommendation: 4.1.1.RELEASE


References
Advisory
Release Note
Issue
Issue
Commit
Commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant