Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
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 SpEL Expression injection vulnerabilities in an interactive lesson.
Start learningUpgrade org.springframework.data:spring-data-mongodb
to version 3.3.5, 3.4.1 or higher.
Affected versions of this package are vulnerable to SpEL Expression injection when using @Query
or @Aggregation-annotated
query methods with SpEL
expressions. Exploiting this vulnerability is possible if the query parameter placeholders contain unsanitized value binding.
Notes:
Applications are not affected if one of the followings is true:
The annotated repository query or aggregation method does not contain expressions
The annotated repository query or aggregation method does not use the parameter placeholder syntax within the expression
The user-supplied input is sanitized by the application
The repository is configured to use a QueryMethodEvaluationContextProvider
that limits SpEL
usage
If upgrading to the fixed version is not possible, the following mitigation steps should be taken:
Rewrite query or aggregation declarations to use parameter references (“[0]” instead of “?0“) within the expression.
Sanitize parameters before calling the query method.
Reconfigure the repository factory bean through a BeanPostProcessor
with a limited QueryMethodEvaluationContextProvider
.