Skip to content

← Public intelligence

Packagist package

doctrine/orm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedPackagistPublished

    doctrine/orm Regression in Query Parenthesis can have Security Implications

    GHSA-vjrg-wpm8-rhrw

    Affected
    • Packagist doctrine/orm >= 2.8.3, < 2.8.4
    Fixed in
    2.8.4· Vendor fix available
    Issue
    An issue identified in doctrine/orm project related to statement in Where-Clause were not wrapped in brackets due to improper hadandling of case insensitive check.

    Recommended action: Upgrade to 2.8.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedPackagistPublished

    Doctrine SQL injection vulnerability

    GHSA-6q9v-4hq6-5m67

    Affected
    • Packagist doctrine/orm >= 2.0.0, < 2.0.3; >= 1.0.0, < 1.2.4
    Fixed in
    2.0.31.2.4· Vendor fix available
    Issue
    Doctrine is prone to SQL injection vulnerability. Users of Doctrine 1.2 and 2 should update to the newly released versions of both libraries immediately. Both versions only include the security fix and no other changes to their previous versions 1.2.3 and 2.0.2. Affected versions are: - 1.2.3 and earlier for PostgreSQL and DB2 Dialects - 2.0.2 and earlier The security issue was found to affect the Doctrine\DBAL\Platforms\AbstractPlatform::modifyLimitQuery() function which does not cast input values for limit and offset to integer and allows malicious SQL to be executed if these parameters are passed into Doctrine 2 directly from request variables without previous cast to integer. Functionality building on top using limit queries in the ORM such as Doctrine\ORM\Query::setFirstResult() and Doctrine\ORM\Query::setMaxResults() are also affected by this security issue. The fix for this security issue breaks backwards compatibility for developers that extend the…

    Recommended action: Upgrade to 2.0.3 or 1.2.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →