skip to content
Back to
Home Bounties Research Advisories CodeQL Wall of Fame Get Involved Events
March 25, 2020

GHSL-2020-028: Server-Side Template Injection in Netflix Titus

Alvaro Munoz


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




Netflix Titus

Tested Version


Issues found

GHSL-2020-028 Details - Remote Code Execution - JavaEL Injection

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

Netflix Titus uses Java Bean Validation (JSR 380) custom constraint validators such as 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, they 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 boolean isValid(Container container, ConstraintValidatorContext context) {
    if (container == null) {
        return true;
    Set<String> common = new HashSet<>(container.getSoftConstraints().keySet());
    if (common.isEmpty()) {
        return true;
            "Soft and hard constraints not unique. Shared constraints: " + common
    return false;

We found multiple paths flowing into ConstraintValidatorContext.buildConstraintViolationWithTemplate(0).


This issue may lead to Remote Code execution


There are different approaches to remediate the issue:

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). We would like to thank Guillaume Smet from the Hibernate Validator team for help with the remediation advice.


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