CVE-2014-2685
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 · uneditedThe GenericConsumer class in the Consumer component in ZendOpenId before 2.0.2 and the Zend_OpenId_Consumer class in Zend Framework 1 before 1.12.4 violate the OpenID 2.0 protocol by ensuring only that at least one field is signed, which allows remote attackers to bypass authentication by leveraging an assertion from an OpenID provider.
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 confidenceThe Zend Framework OpenID consumer implementation (Zend_OpenId_Consumer class) and GenericConsumer class fail to properly validate OpenID 2.0 protocol requirements. The code only verifies that at least one field is signed, rather than requiring all critical assertion fields to be signed, allowing attackers to bypass authentication by submitting partially signed assertions.
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<= 1.12.3= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.5.0= 1.5.1= 1.5.2= 1.5.3= 1.6.0= 1.6.1<= 2.0.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Locate Zend Framework installationSearch for Zend library files on the system. Look for directories containing 'Zend' or 'ZendFramework' naming, typically in PHP include_path, composer vendor directory, or application lib folders.Affected if Zend Framework library is found on the system
-
Determine Zend Framework versionCheck for a Version.php or similar file within the Zend library directory. Common paths include Zend/Version.php or vendor/zendframework/zendframework/library/Zend/Version.php. Read the version constant defined in the file.Affected if The installed version is 1.12.3 or lower, or is one of these exact versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.6.0, or 1.6.1
-
Check for ZendOpenId consumer usageSearch application source code for imports or includes of Zend_OpenId_Consumer class, Zend_OpenId_GenericConsumer class, or references to 'Zend_OpenId'. Also check composer.json or package files for zendframework/zendopenid dependency.Affected if The application uses Zend_OpenId_Consumer or Zend_OpenId_GenericConsumer for OpenID authentication
-
Verify OpenID protocol handlingIf OpenID consumer is in use, examine the code that processes OpenID assertions. Look for the validation logic that handles signed fields in OpenID responses. The vulnerable code checks for 'at least one' signed field rather than validating all critical fields per OpenID 2.0 spec.Affected if The OpenID assertion processing does not validate that all critical assertion fields are signed (only checks that at least one field is signed)
A user is affected if their system has Zend Framework 1.12.3 or lower (or specific point versions listed) or ZendOpenId 2.0.1 or lower, AND the OpenID consumer component is actively used for authentication.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to ZendOpenId 2.0.2 or Zend Framework 1.12.4 or later, which enforce proper validation of all signed fields per OpenID 2.0 specification. Audit existing OpenID integrations for authentication dependencies.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2685 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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