dbcve.org
FrameworkApplication · Zend

CVE-2015-0270

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-25
Fix available
A fix is available. Upgrade to 2.2.10 / 2.3.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zend Framework before 2.2.10 and 2.3.x before 2.3.5 has Potential SQL injection in PostgreSQL Zend\Db adapter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the PostgreSQL adapter of Zend\Db component in Zend Framework. The vulnerability allows attackers to inject malicious SQL queries through improperly sanitized user input processed by the database adapter.

MitigationUpgrade Zend Framework to version 2.2.10, 2.3.5 or later to patch the SQL injection vulnerability in the PostgreSQL adapter. Review and test all database query paths that use user-supplied input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FrameworkApplication
Affected:< 2.2.10>= 2.3.0, < 2.3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Zend Framework version
    Check your composer.json file for the 'zend-framework/zend-framework' or 'zendframework/zend-framework' package version, or run 'composer show zend-framework/zend-framework' if installed via Composer
    Affected if Version is less than 2.2.10 OR between 2.3.0 and 2.3.4 (inclusive)
  2. Confirm PostgreSQL adapter is in use
    Search your codebase for usage of 'Zend\Db\Adapter\Driver\Pdo\Connection' with 'pgsql' or references to 'Zend\Db\Adapter\Adapter' configured with 'driver' => 'Pdo\Pgsql'
    Affected if The application uses Zend\Db with a PostgreSQL database connection
  3. Review database query implementations
    Search your application code for Zend\Db query methods (such as 'query()', 'select()', 'execute()') that process user-supplied input (GET, POST, or request parameters)
    Affected if User input is directly passed to database query methods without additional sanitization
  4. Check for parameterized queries
    Examine your Zend\Db query code to determine if Prepared Statements with bound parameters are used, or if input is concatenated/interpolated into SQL strings
    Affected if Queries concatenate user input directly into SQL rather than using parameterized queries

Your environment is affected if you run a Zend Framework version between 2.3.0-2.3.4 or below 2.2.10, use the PostgreSQL adapter, and pass unsanitized user input to database queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.10 / 2.3.5 or later
Fixed in 2.2.102.3.5
Interim mitigation

Upgrade Zend Framework to version 2.2.10, 2.3.5 or later to patch the SQL injection vulnerability in the PostgreSQL adapter. Review and test all database query paths that use user-supplied input.

Recommended fix High confidence

Zend Framework 2.2.10 or 2.3.5 (or later stable releases)

  1. Check current Zend Framework version in your composer.json or lock file
  2. Update composer.json to require Zend Framework version 2.2.10 or higher (for 2.2.x branch) or 2.3.5 or higher (for 2.3.x branch)
  3. Run 'composer update zendframework/zendframework' to install the fixed version
  4. Verify the update was successful by checking the installed version with 'composer show zendframework/zendframework'
  5. Test your application thoroughly, particularly any database operations using the PostgreSQL Zend\Db adapter
Caveat Minor version upgrades in Zend Framework 2.x typically maintain backward compatibility, but test thoroughly as with any framework update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Framework Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0270 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data