org.springframework.security vulnerabilities

Products

• org.springframework.security/spring-security-core 31
• org.springframework.security/spring-security-web 7
• org.springframework.security/spring-security-config 5
• org.springframework.security/spring-security-oauth2-authorization-server 4
• org.springframework.security/spring-security-saml2-service-provider 4
• org.springframework.security/spring-security-oauth2-client 2
• org.springframework.security/spring-security-oauth2-jose 2
• org.springframework.security/spring-security-aspects 1
• org.springframework.security/spring-security-bom 1
• org.springframework.security/spring-security-cas 1
• org.springframework.security/spring-security-crypto 1

Latest org.springframework.security CVEs

Newest publication first · page 3 of 3

1. CVE-2011-2732 Improper Control of Generation of Code in Spring Security

   Published 2012-12-05

   Medium·CVSS 4.3 EPSS 4.6%

   CRLF injection vulnerability in the logout functionality in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the spring-security-redirect parameter.

2. CVE-2011-2894 Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data

   Published 2011-10-04

   Medium·CVSS 6.8 EPSS 8.6%

   Spring Framework 3.0.0 through 3.0.5, Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6, and possibly other versions deserialize objects from untrusted sources, which allows remote attackers to bypass intended security restrictions and execute untrusted code by (1) seri...

3. CVE-2010-3700 Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security

   Published 2010-10-29

   Medium·CVSS 5.0 EPSS 1.7%

   VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.