The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Missing Authorization vulnerabilities in an interactive lesson.
Start learningUpgrade org.springframework.security:spring-security-config
to version 6.3.2 or higher.
org.springframework.security:spring-security-config is a security configuration package for Spring Framework.
Affected versions of this package are vulnerable to Missing Authorization. When the applications using @AuthorizeReturnObject
or the Spring Security produced AuthorizationAdvisorProxyFactory
@Bean
to wrap objects, they may not have all security advice applied, resulting in annotations like @PreFilter
and @PreAuthorize
may take no effect on these wrapped objects.
NOTE:
This does not impact any @Beans
that use Spring Security's method security advice.
For this to impact an application, all of the following need to be true:
AnnotationAwareAspectJAutoProxyCreator
must be the auto proxy creator being used to create proxies; this can either be done declaratively by your application or enabled via @EnableAspectJAutoProxy
or enabled by Spring Boot by virtue of using spring-aspects or a starter that uses spring-aspects
The application must have at least one FactoryBean
present in the application context.
The application must enable method security with @EnableMethodSecurity
The application must wrap objects using the @AuthorizeReturnObject
annotation or the AuthorizationAdvisorProxyFactory
@Bean` produced by Spring Security.
The application must be using @PreFilter
, @PostFilter
, @PreAuthorize
, or @PostAuthorize
on those wrapped objects