GHSA-7g7c-qhf3-x59p: Propel/propel1 SQL Injection Vulnerability

CRITICAL
CVSS 9.8
CWE-89
Published
Advisory Summary

GHSA-7g7c-qhf3-x59p is a CRITICAL (CVSS 9.8) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Propel/propel1 libraries in the Packagist ecosystem. The issue involves propel/propel1 sql injection possible with limit() on mysql. Remediation is available by upgrading affected packages to version 1.7.2.

GHSA-7g7c-qhf3-x59p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7g7c-qhf3-x59p
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Affected Product Propel/propel1
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-7g7c-qhf3-x59p

To remediate this vulnerability, upgrade all affected Propel/propel1 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

propel/propel1 fixed: 1.7.2
Upgrade propel/propel1 to 1.7.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for propel/propel1

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7g7c-qhf3-x59p, inspect your project dependencies for Propel/propel1:

inspect dependencies for propel/propel1

Analyze the terminal output to locate any version of Propel/propel1 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where the product constructs all or part of an sql command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended sql command when it is sent to a downstream component. without sufficient removal or quoting of sql syntax in user-controllable inputs, the generated sql query can cause those inputs to be interpreted as sql instead of ordinary user data. In Propel/propel1, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 Criteria::setLimit() or in DBMySQL::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.

GHSA-7g7c-qhf3-x59p Affected Propel/propel1 Versions

1 component(s)
Fixed Versions:
1.7.2
Product / Package Ecosystem Affected Versions Fixed Version
propel/propel1
Packagist
≥ 1
< 1.7.2
1.7.2

References

Frequently Asked Questions

What is GHSA-7g7c-qhf3-x59p?
GHSA-7g7c-qhf3-x59p is a security vulnerability in Propel/propel1 involving propel/propel1 SQL injection possible with limit() on MySQL under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').
Which Propel/propel1 versions are affected?
Affected versions include releases prior to 1.7.2 across affected packages: propel/propel1.
What version fixes GHSA-7g7c-qhf3-x59p?
Upgrading to 1.7.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is propel/propel1 affected?
Yes, propel/propel1 is affected in releases prior to 1.7.2. Upgrade your dependency to 1.7.2 or later.
What is the CVSS score of GHSA-7g7c-qhf3-x59p?
GHSA-7g7c-qhf3-x59p has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-7g7c-qhf3-x59p?
GHSA-7g7c-qhf3-x59p is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.).
How can I check Packagist dependencies for GHSA-7g7c-qhf3-x59p?
Run the dependency tree command: 'inspect dependencies for propel/propel1'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7g7c-qhf3-x59p",
  "modified" : "2024-05-20T17:36:29Z",
  "published" : "2024-05-20T17:36:28Z",
  "aliases" : [ ],
  "summary" : "propel/propel1 SQL injection possible with limit() on MySQL",
  "details" : "The limit() query method is susceptible to catastrophic SQL injection with MySQL.\n\nFor example, given a model User for a table users:\n```\nUserQuery::create()->limit('1;DROP TABLE users')->find();\n```\nThis will drop the users table!\n\nThe cause appears to be a lack of integer casting of the limit input in either Criteria::setLimit() or in DBMySQL::applyLimit(). The code comments there seem to imply that casting was avoided due to overflow issues with 32-bit integers.\n\nThis is surprising behavior since one of the primary purposes of an ORM is to prevent basic SQL injection.\n\nThis affects all versions of Propel: 1.x, 2.x, and 3.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "propel/propel1"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1"
      }, {
        "fixed" : "1.7.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.7.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/propelorm/Propel/issues/1052"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/propelorm/Propel/pull/1054"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/propelorm/Propel/commit/b72093201f8e225410f62a246653ac039e31c90a"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/propel/propel1/2018-02-14.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/propelorm/Propel"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-89" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-20T17:36:28Z",
    "nvd_published_at" : null
  }
}