CVE-2019-16768

Internal exception message exposure for login action

Workarounds

The src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig file should be overridden and lines https://github.com/Sylius/Sylius/blob/1.4/src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig#L13-L17 should be replaced with

        {% if last_error %}
            <div class="ui left aligned basic segment">
                {{ messages.error(last_error.messageKey) }}
            </div>
        {% endif %}

The messageKey field should be used instead of the message.

Exception messages from internal exceptions (like database exception) are wrapped by \Symfony\Component\Security\Core\Exception\AuthenticationServiceException and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer.

A validation message with the exception details will be presented to the user when one will try to log into the shop.

CVE-2019-16768 has a CVSS score of 3.5 (Low). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.14, 1.4.10, 1.5.7, 1.6.3); upgrading removes the vulnerable code path.

Kodem intelligence

Has the problem been patched? What versions should users upgrade to?

1. What is CVE-2019-16768? CVE-2019-16768 is a low-severity security vulnerability in sylius/sylius (composer), affecting versions < 1.3.14. It is fixed in 1.3.14, 1.4.10, 1.5.7, 1.6.3.
2. How severe is CVE-2019-16768? CVE-2019-16768 has a CVSS score of 3.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sylius/sylius are affected by CVE-2019-16768? sylius/sylius (composer) versions < 1.3.14 is affected.
4. Is there a fix for CVE-2019-16768? Yes. CVE-2019-16768 is fixed in 1.3.14, 1.4.10, 1.5.7, 1.6.3. Upgrade to this version or later.
5. Is CVE-2019-16768 exploitable, and should I be worried? Whether CVE-2019-16768 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2019-16768 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2019-16768?
   • Upgrade sylius/sylius to 1.3.14 or later
   • Upgrade sylius/sylius to 1.4.10 or later
   • Upgrade sylius/sylius to 1.5.7 or later
   • Upgrade sylius/sylius to 1.6.3 or later

Other vulnerabilities in sylius/sylius