CVE-2014-2684
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 does not verify that the openid_op_endpoint value identifies the same Identity Provider as the provider used in the association handle, which allows remote attackers to bypass authentication and spoof arbitrary OpenID identities by using a malicious OpenID Provider that generates OpenID tokens with arbitrary identifier and claimed_id values.
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 GenericConsumer class in ZendOpenId before 2.0.2 and Zend_OpenId_Consumer in Zend Framework 1 before 1.12.4 fail to verify that the openid_op_endpoint value matches the Identity Provider used in the association handle. This allows remote attackers to bypass authentication by using a malicious OpenID Provider that issues tokens with arbitrary identifier and claimed_id values.
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<= 2.0.1<= 1.12.4CVSS 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
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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.
-
Identify ZendOpenId or Zend Framework 1 installationLocate the Zend library files in your codebase. For ZendOpenId, look for files such as GenericConsumer.php or OpenId/Consumer.php within the Zend library directory. For Zend Framework 1, check the Zend/ directory structure.Affected if The Zend library directory contains OpenID consumer components from ZendOpenId or Zend Framework 1.
-
Determine the installed ZendOpenId versionCheck the version information in the ZendOpenId library. Look for a version.php file or version constant within the ZendOpenId directory. If using Composer, check the installed.json or composer.lock file for the zendopenid package version.Affected if The installed version of ZendOpenId is 2.0.1 or earlier.
-
Determine the installed Zend Framework 1 versionCheck the version.php file in the main Zend library directory or within the Version.php file itself. For Composer-based installations, check composer.lock for the zendframework/zendframework1 version.Affected if The installed version of Zend Framework 1 is 1.12.4 or earlier.
-
Verify OpenID consumer functionality is in useSearch your application code for usage of the GenericConsumer class, Zend_OpenId_Consumer class, or OpenID consumer components. Look for includes or require statements referencing these classes.Affected if Your application uses the GenericConsumer or Zend_OpenId_Consumer class for OpenID authentication.
-
Confirm the vulnerable verification is not patchedInspect the GenericConsumer.php or Zend/OpenId/Consumer.php file. Look for the _getAssociationOrVerify method or similar logic that handles openid_op_endpoint verification. Check if the code performs validation that the openid_op_endpoint matches the Identity Provider from the association handle.Affected if The code lacks proper verification of the openid_op_endpoint against the associated Identity Provider.
You are affected if your environment uses ZendOpenId 2.0.1 or earlier, or Zend Framework 1.12.4 or earlier, and your application utilizes the OpenID consumer functionality without the openid_op_endpoint verification fix.
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, Zend Framework 1.12.4, or later versions that implement proper verification of the openid_op_endpoint against the associated Identity Provider.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2684 — 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-2684 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