CVE-2020-5245: Remote Code Execution (RCE) vulnerability in dropwizard-validation

Published Feb 24, 2020
·
Updated

Dropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature.

Summary

A server-side template injection was identified in the self-validating (@SelfValidating) feature of dropwizard-validation enabling attackers to inject arbitrary Java EL expressions, leading to Remote Code Execution (RCE) vulnerability.

If you're using a self-validating bean (via @SelfValidating), an upgrade to Dropwizard 1.3.19 or 2.0.2 is strongly recommended.

Impact

This issue may allow Remote Code Execution (RCE), allowing to run arbitrary code on the host system (with the privileges of the Dropwizard service account privileges) by injecting arbitrary Java Expression Language (EL) expressions when using the self-validating feature (@SelfValidating, @SelfValidation) in dropwizard-validation.

Patches

The issue has been fixed in dropwizard-validation 1.3.19 and 2.0.2. We strongly recommend upgrading to one of these versions.

Workarounds

If you are not able to upgrade to one of the aforementioned versions of dropwizard-validation but still want to use the @SelfValidating feature, make sure to properly sanitize any message you're adding to the ViolationCollector in the method annotated with @SelfValidation.

Example: java @SelfValidation public void validateFullName(ViolationCollector col) { if (fullName.contains("")) { // Sanitize fullName variable by escaping relevant characters such as "$" col.addViolation("Full name contains invalid characters: " + sanitizeJavaEl(fullName)); } }

See also: https://github.com/dropwizard/dropwizard/blob/v2.0.2/dropwizard-validation/src/main/java/io/dropwizard/validation/selfvalidating/ViolationCollector.java#L84-L98

References

https://github.com/dropwizard/dropwizard/pull/3157 https://github.com/dropwizard/dropwizard/pull/3160 https://docs.oracle.com/javaee/7/tutorial/jsf-el.htm https://docs.jboss.org/hibernate/validator/6.1/reference/en-US/htmlsingle/#section-interpolation-with-message-expressions https://beanvalidation.org/2.0/spec/#validationapi-message-defaultmessageinterpolation

For more information

If you have any questions or comments about this advisory: Open an issue in dropwizard/dropwizard Start a discussion on the dropwizard-dev mailing list

Security contact

If you want to responsibly disclose a security issue in Dropwizard or one of its official modules, please contact us via the published channels in our security policy:

https://github.com/dropwizard/dropwizard/security/policy#reporting-a-vulnerability

Other sources

Dropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature.

The issue has been fixed in dropwizard-validation 1.3.19 and 2.0.2.

MITRE

Affected Software

5 affected componentsFixes available
Dropwizard Dropwizard Validation<1.3.19
Dropwizard Dropwizard Validation>=2.0.0<2.0.2
Oracle Blockchain Platform<21.1.2
maven/io.dropwizard:dropwizard-validation>=1.3.0-rc1<1.3.19
1.3.19
maven/io.dropwizard:dropwizard-validation>=2.0.0<2.0.2
2.0.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.dropwizard:dropwizard-validation to a version that resolves this vulnerability.

    Fixed in 1.3.19
  2. Upgrade

    Upgrade maven/io.dropwizard:dropwizard-validation to a version that resolves this vulnerability.

    Fixed in 2.0.2
  3. Upgrade

    Upgrade dropwizard-validation to a version that resolves this vulnerability.

    Fixed in 1.3.19
  4. Upgrade

    Upgrade dropwizard-validation to a version that resolves this vulnerability.

    Fixed in 2.0.2
  5. Configuration

    If you cannot upgrade, properly sanitize any message added to ViolationCollector in the method annotated with @SelfValidation when using @SelfValidating; for example, sanitize input such as fullName before concatenating it into col.addViolation(...).

    dropwizard-validation (@SelfValidation / ViolationCollector message handling) sanitizeJavaEl(message) = Escaping relevant characters such as "$" (e.g., via sanitizeJavaEl(fullName))

Event History

Feb 24, 2020
Advisory Published
via GitHub·05:27 PM
Data Sourced
via GitHub·05:27 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·05:35 PM
Data Sourced
via MITRE·05:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 9, 58461
Event
12:29 PM

Frequently Asked Questions

1

What is the vulnerability ID for this vulnerability?

The vulnerability ID for this vulnerability is CVE-2020-5245.

2

What is the severity of CVE-2020-5245?

The severity of CVE-2020-5245 is critical with a CVSS score of 8.8.

3

How does CVE-2020-5245 allow arbitrary code execution on the host system?

CVE-2020-5245 allows arbitrary code execution on the host system by injecting arbitrary Java Expression Language expressions when using the self-validating feature of Dropwizard-Validation.

4

Which versions of Dropwizard-Validation are affected by CVE-2020-5245?

Dropwizard-Validation versions before 1.3.19 and versions between 2.0.0 and 2.0.2 are affected by CVE-2020-5245.

5

How can I fix CVE-2020-5245?

To fix CVE-2020-5245, update Dropwizard-Validation to version 1.3.19 or higher for versions before 2.0.0, or update to version 2.0.2 or higher for versions between 2.0.0 and 2.0.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203