skip to content
Back to
Home Research Advisories CodeQL Wall of Fame Get Involved Events
May 11, 2020

GHSL-2020-029: Server-Side template injection in Apache Syncope (RCE) - CVE-2020-1959

Alvaro Munoz


A Server-Side Template Injection was identified in Apache Syncope enabling attackers to inject arbitrary Java EL expressions, leading to a Remote Code Execution (RCE) vulnerability.


Apache Syncope

Tested Version


Issues found

GHSL-2020-029 Details - Remote Code Execution - JavaEL Injection (CVE-2020-1959)

It is possible to run arbitrary code on the server (with Syncope service account privileges) by injecting arbitrary Java Expression Language (EL) expressions.

Apache Syncope uses Java Bean Validation (JSR 380) custom constraint validators such as org.apache.syncope.core.persistence.jpa.validation.entity.AnyObjectValidator When building custom constraint violation error messages, it is important to understand that they support different types of interpolation, including Java EL expressions. Therefore if an attacker can inject arbitrary data in the error message template being passed to ConstraintValidatorContext.buildConstraintViolationWithTemplate() argument, he will be able to run arbitrary Java code. Unfortunately, it is common that validated (and therefore, normally untrusted) bean properties flow into the custom error message.

public class AnyObjectValidator extends AbstractValidator<AnyObjectCheck, AnyObject> {

    public boolean isValid(final AnyObject anyObject, final ConstraintValidatorContext context) {

        boolean isValid = anyObject.getName() != null && KEY_PATTERN.matcher(anyObject.getName()).matches();

        if (!isValid) {
                    getTemplate(EntityViolationType.InvalidName, anyObject.getName())).

        return isValid;

There are a total of 25 validators using ConstraintValidatorContext.buildConstraintViolationWithTemplate(0) out of which 20 appear to be vulnerable (reflecting validated value in the error message)


This issue may lead to Remote Code execution.


There are different approaches to remediate the issue:

This issue was addressed in the following commit.


Coordinated Disclosure Timeline

This report was subject to the GHSL coordinated disclosure policy.

Supporting Resources


This issue was discovered and reported by GHSL team member @pwntester (Alvaro Muñoz).


You can contact the GHSL team at, please include the GHSL-2020-029 in any communication regarding this issue.