The escaping of offset and length inputs to the generation of a LIMIT clause was not probably cast to an integer, allowing SQL injection to take place if application developers passed unescaped user input to the DBAL QueryBuilder or any other API that ultimately uses the AbstractPlatform::modifyLimitQuery API. Upstream Reference: https://github.com/doctrine/dbal/security/advisories/GHSA-r7cj-8hjg-x622 https://github.com/doctrine/dbal/releases
Created php-doctrine-dbal tracking bugs for this issue: Affects: epel-7 [bug 2035269] Affects: fedora-all [bug 2035268]