dbcve.org
Debian LinuxOperating system · Debian

CVE-2015-7695

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-07
Fix available
A fix is available. Upgrade to after 1.12.15 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
The PDO adapters in Zend Framework before 1.12.16 do not filer null bytes in SQL statements, which allows remote attackers to execute arbitrary SQL commands via a crafted query.

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

The PDO adapters in Zend Framework versions before 1.12.16 fail to sanitize null bytes in SQL statements, allowing attackers to inject arbitrary SQL commands through crafted queries containing null byte characters.

MitigationUpgrade to Zend Framework 1.12.16 or later which includes null byte filtering, or implement input validation to strip null bytes from all SQL query parameters before execution.

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
Debian LinuxOperating system
Affected:= 7.0= 8.0
Zend FrameworkApplication
Affected:<= 1.12.15

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.0/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 Zend Framework version
    Locate the Zend Framework library in your application (typically in a 'Zend' or 'library/Zend' directory) and check the Version.php file or the release notes. Run: grep -r 'VERSION' Zend/Version.php 2>/dev/null || find . -name 'Version.php' -path '*/Zend/*' -exec cat {} \;
    Affected if The installed version is 1.12.15 or earlier, or the version cannot be determined and the library predates the 1.12.16 release
  2. Confirm PDO database adapter is in use
    Search your application codebase for PDO-related database adapter usage. Run: grep -r 'Pdo_' Zend/Db/Adapter/ | head -20, or check your database configuration for adapter type 'Pdo_Mysql', 'Pdo_Pgsql', 'Pdo_Sqlite', etc.
    Affected if Your application uses any PDO-based Zend_Db adapter (Pdo_Mysql, Pdo_Pgsql, Pdo_Sqlite, Pdo_Oci, etc.)
  3. Check for SQL query execution paths
    Review your application code to identify where SQL queries are constructed and executed using Zend_Db. Look for calls to $db->query(), $db->fetchAll(), $select->query(), or prepare/execute patterns with Zend_Db.
    Affected if Your application executes SQL queries through Zend_Db and accepts user-supplied parameters that could reach these queries
  4. Inspect input handling for null byte filtering
    Search your codebase for null byte handling in SQL-related code. Run: grep -rn '\\x00' your/app/path/ | grep -i -E '(sql|query|param|bind)' or check if your application strips null bytes before passing data to database queries
    Affected if User input containing null byte characters (%00 URL-encoded or literal \0) is passed to SQL queries without being filtered or rejected

You are affected if you are running Zend Framework 1.12.15 or earlier, using PDO database adapters, and your application does not filter null bytes from SQL query parameters before execution.

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 a release after 1.12.15
Interim mitigation

Upgrade to Zend Framework 1.12.16 or later which includes null byte filtering, or implement input validation to strip null bytes from all SQL query parameters before execution.

Recommended fix High confidence

Zend Framework 1.12.16 or later (or Debian security update package containing the fixed version)

  1. For Zend Framework applications: Upgrade Zend Framework from any version <= 1.12.15 to version 1.12.16 or later
  2. If using Composer, run: `composer require zendframework/zendframework:1.12.16` or update your composer.json to specify "zendframework/zendframework": ">=1.12.16"
  3. For Debian systems: Run `apt-get update && apt-get install libzend-framework-php` or `apt-get upgrade` to apply the Debian security package containing the fixed version
  4. After upgrading, verify the fix by checking that the Zend Framework version is >= 1.12.16: `composer show zendframework/zendframework version`
  5. Test your application to ensure the upgrade does not break existing functionality
Caveat Zend Framework 1.12.16 is a security patch release; minimal breaking changes expected, but test in non-production first

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7695 — 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-7695 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