Homepage
About Snyk

SpEL Expression injection Affecting org.springframework.data:spring-data-mongodb package, versions [,3.3.5) [3.4.0,3.4.1)

0.0
critical

Snyk CVSS

    Attack Complexity High
    Scope Changed
    Confidentiality High
    Integrity High
    Availability High

    Threat Intelligence

    Exploit Maturity Proof of concept
    EPSS 0.45% (75th percentile)
Expand this section
NVD
9.8 critical

Do your applications use this vulnerable package?

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 applications
  • Snyk ID SNYK-JAVA-ORGSPRINGFRAMEWORKDATA-2932975
  • published 21 Jun 2022
  • disclosed 21 Jun 2022
  • credit Zewei Zhang
Report a new vulnerability Found a mistake?

Introduced: 21 Jun 2022

CVE-2022-22980 Open this link in a new tab
CWE-917 Open this link in a new tab

How to fix?

Upgrade org.springframework.data:spring-data-mongodb to version 3.3.5, 3.4.1 or higher.

Overview

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:

  1. The annotated repository query or aggregation method does not contain expressions

  2. The annotated repository query or aggregation method does not use the parameter placeholder syntax within the expression

  3. The user-supplied input is sanitized by the application

  4. The repository is configured to use a QueryMethodEvaluationContextProvider that limits SpEL usage

Workaround:

If upgrading to the fixed version is not possible, the following mitigation steps should be taken:

  1. Rewrite query or aggregation declarations to use parameter references (“[0]” instead of “?0“) within the expression.

  2. Sanitize parameters before calling the query method.

  3. Reconfigure the repository factory bean through a BeanPostProcessor with a limited QueryMethodEvaluationContextProvider.