dbcve.org
Debian LinuxOperating system · Debian

CVE-2014-4914

CRITICAL · 9.8 CVSS v3.0 Published 2017-12-29
Fix available
A fix is available. Upgrade to 1.12.7 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 Zend_Db_Select::order function in Zend Framework before 1.12.7 does not properly handle parentheses, which allows remote attackers to conduct SQL injection attacks via unspecified vectors.

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 · moderate confidence

The Zend_Db_Select::order function in Zend Framework versions prior to 1.12.7 fails to properly sanitize or escape parentheses in user-supplied input. This allows remote attackers to inject arbitrary SQL statements through the order clause by crafting malicious input containing parentheses that break out of the intended ORDER BY context.

MitigationUpgrade to Zend Framework 1.12.7 or later, which contains the fix for proper parentheses handling. Alternatively, implement strict input validation/sanitization on all values passed to Zend_Db_Select::order() before use.

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.7

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 directory and check the Version.php file or library changelog for the installed version number. Common paths include /usr/share/zend-framework/library/Zend/Version.php or a vendor/zend-framework directory in your project.
    Affected if The installed version is less than 1.12.7
  2. Confirm Debian package version if using system packages
    Run 'dpkg -l | grep zend' or 'apt-cache policy zend-framework' to check if the Debian system package version is 1.12.7 or later.
    Affected if The installed Debian package version is below 1.12.7-1 or the specific fixed Debian versions for 7.0/8.0
  3. Identify usage of Zend_Db_Select::order()
    Search your codebase for calls to the order() method on Zend_Db_Select objects. Search patterns: '$select->order(' or 'Zend_Db_Select' combined with 'order'.
    Affected if Your application code contains Zend_Db_Select::order() calls that accept external input
  4. Check if user input reaches order() without sanitization
    Trace the data flow from request parameters ($_GET, $_POST, etc.) to the order() method. Verify whether input passes through $db->quote() or other escaping functions before being used in the order clause.
    Affected if User-supplied values from request parameters are passed directly to order() without escaping parentheses or using parameterized queries

You are affected if your installed Zend Framework version is below 1.12.7 AND your application passes unsanitized user input to the Zend_Db_Select::order() method.

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 1.12.7 or later
Fixed in 1.12.7
Interim mitigation

Upgrade to Zend Framework 1.12.7 or later, which contains the fix for proper parentheses handling. Alternatively, implement strict input validation/sanitization on all values passed to Zend_Db_Select::order() before use.

Recommended fix High confidence

Zend Framework 1.12.7

  1. 1. Identify the current Zend Framework version in use by examining the library files or project dependencies
  2. 2. Download Zend Framework 1.12.7 or later from the official framework.zend.com repository
  3. 3. Replace the existing Zend Framework library files with the new version, ensuring all Zend/ subdirectories are updated
  4. 4. Verify the upgrade by checking that Zend Framework version now reports 1.12.7 or higher
  5. 5. Test application functionality to ensure the upgrade does not break existing features
Caveat Zend Framework 1.x is older series; ensure compatibility with PHP version and any custom components

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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