HighGHSA-p4pj-9g59-4ppvCVE-2020-15143

Remote Code Execution in SyliusResourceBundle

Published 19 Aug 2020 · Updated 8 Jul 2026

Is your project on an affected sylius/resource-bundle?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.4.0 <1.4.7
Fixed in
1.4.7
Update to the fixed version for your release line, for example:composer require sylius/resource-bundle:^1.4.7
Affected
>=1.5.0 <1.5.2
Fixed in
1.5.2
Update to the fixed version for your release line, for example:composer require sylius/resource-bundle:^1.5.2
Affected
>=1.6.0 <1.6.4
Fixed in
1.6.4
Update to the fixed version for your release line, for example:composer require sylius/resource-bundle:^1.6.4
Affected
>=1.0.0 <1.3.14
Fixed in
1.3.14
Update to the fixed version for your release line, for example:composer require sylius/resource-bundle:^1.3.14

Details

Impact

Request parameters injected inside an expression evaluated by symfony/expression-language package haven't been sanitized properly. This allows the attacker to access any public service by manipulating that request parameter, allowing for Remote Code Execution.

The vulnerable versions include: <=1.3.13 || >=1.4.0 <=1.4.6 || >=1.5.0 <=1.5.1 || >=1.6.0 <=1.6.3.

Example

foo:
    path: /foo/{id}
    defaults:
        _sylius:
            repository:
                method: findSome
                arguments:
                    entity: "expr:service('repository').find($id)"

In this case, $id can be prepared in a way that calls other services.

If you visit /foo/"~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~", it will result in a following expression expr:service('repository').find(""~service('doctrine').getManager().getConnection().executeQuery("DELETE * FROM TABLE")~""), which will execute a query on the currently connected database.

To find a vulnerability in your application, look for any routing definition that uses request parameters inside expression language.

Patches

This issue has been patched for versions 1.3.14, 1.4.7, 1.5.2 and 1.6.4. Versions prior to 1.3 were not patched.

Workarounds

The fix requires adding addslashes in ParametersParser::parseRequestValueExpression to sanitize user input before evaluating it using the expression language.

- return is_string($variable) ? sprintf('"%s"', $variable) : $variable;
+ return is_string($variable) ? sprintf('"%s"', addslashes($variable)) : $variable;

Acknowledgements

This security issue has been reported by Craig Blanchette (@isometriks), thanks a lot!

For more information

If you have any questions or comments about this advisory:

  • Email us at [security@sylius.com](mailto:security@sylius.com)

Is GHSA-p4pj-9g59-4ppv in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sylius/resource-bundle, and gives you the command that fixes it.

More advisories for sylius/resource-bundle

  • MediumGHSA-65v7-wg35-2qpmSylius Resource Bundle Cross-Site Request Forgery vulnerability · 29 May 2024
  • CriticalCVE-2020-15146Remote Code Execution in SyliusResourceBundle · 19 Aug 2020
  • MediumCVE-2020-5218Ability to expose data in Sylius by using an unintended serialisation group · 31 Jan 2020
sylius/resource-bundle security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.