p PatchFirst

GHSA-7vw7-qx38-37vr

GHSA-7vw7-qx38-37vr · Propel2 SQL injection possible with limit() on MySQL

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

The limit() query method is susceptible to catastrophic SQL injection with MySQL. For example, given a model User for a table users: ``` UserQuery::create()->limit('1;DROP TABLE users')->find(); ``` This will drop the users table! The cause appears to be a lack of integer casting of the limit input in either Propel\Runtime\ActiveQuery\Criteria::setLimit() or in Propel\Runtime\Adapter\Pdo\MysqlAdapter::applyLimit(). The code comments there seem to imply that casting was avoided due to overflow issues with 32-bit integers. This is surprising behavior since one of the primary purposes of an ORM is to prevent basic SQL injection. This affects all versions of Propel: 1.x, 2.x, and 3.

CVSS 9.8 · Critique · Correctif disponible

Publication
Mise à jour

Pile logicielle: php

Produits et versions concernés

  • propel/propel Packagist

    Versions du logiciel
    • 2.0.0-alpha1
    • 2.0.0-alpha2
    • 2.0.0-alpha3
    • 2.0.0-alpha4
    • 2.0.0-alpha5
    • 2.0.0-alpha6
    • 2.0.0-alpha7
    Plages de versions concernées
    • ECOSYSTEM: ≥ 2.0.0-alpha1, < 2.0.0-alpha8

    Mettez à jour vers 2.0.0-alpha8

Sources originales

Vérifiez votre serveur →