What is CVE-2014-2682?

CVE-2014-2682 is a medium-severity XML external entity injection (XXE) vulnerability in zendframework/zendframework1 (composer), affecting versions < 1.12.4. It is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.

Which packages are affected by CVE-2014-2682?

zendframework/zendframework1 (composer) versions < 1.12.4; zendframework/zendopenid (composer) versions < 2.0.2; zendframework/zendrest (composer) versions < 2.0.2; zendframework/zendservice-audioscrobbler (composer) versions < 2.0.2; zendframework/zendservice-nirvanix (composer) versions < 2.0.2; zendframework/zendservice-slideshare (composer) versions < 2.0.2; zendframework/zendservice-technorati (composer) versions < 2.0.2; zendframework/zendservice-windowsazure (composer) versions < 2.0.2; zendframework/zendservice-amazon (composer) versions < 2.0.3; zendframework/zendservice-api (composer) versions < 1.0.0.

Is there a fix for CVE-2014-2682?

Yes. CVE-2014-2682 is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. Upgrade to this version or later.

Is CVE-2014-2682 exploitable, and should I be worried?

Whether CVE-2014-2682 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-2682 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2014-2682 in zendframework/zendframework1

Q: Which packages are affected by CVE-2014-2682?

zendframework/zendframework1 (composer) versions < 1.12.4; zendframework/zendopenid (composer) versions < 2.0.2; zendframework/zendrest (composer) versions < 2.0.2; zendframework/zendservice-audioscrobbler (composer) versions < 2.0.2; zendframework/zendservice-nirvanix (composer) versions < 2.0.2; zendframework/zendservice-slideshare (composer) versions < 2.0.2; zendframework/zendservice-technorati (composer) versions < 2.0.2; zendframework/zendservice-windowsazure (composer) versions < 2.0.2; zendframework/zendservice-amazon (composer) versions < 2.0.3; zendframework/zendservice-api (composer) versions < 1.0.0.

Q: Is there a fix for CVE-2014-2682?

Yes. CVE-2014-2682 is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. Upgrade to this version or later.

Q: Is CVE-2014-2682 exploitable, and should I be worried?

Whether CVE-2014-2682 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-2682 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-2682?

Upgrade: zendframework/zendframework1 to 1.12.4 or later, zendframework/zendopenid to 2.0.2 or later, zendframework/zendrest to 2.0.2 or later, zendframework/zendservice-audioscrobbler to 2.0.2 or later, zendframework/zendservice-nirvanix to 2.0.2 or later, zendframework/zendservice-slideshare to 2.0.2 or later, zendframework/zendservice-technorati to 2.0.2 or later, zendframework/zendservice-windowsazure to 2.0.2 or later, zendframework/zendservice-amazon to 2.0.3 or later, zendframework/zendservice-api to 1.0.0 or later.

Summary

Several Zend Products Vulnerable to XXE and XEE attacks

Zend Framework 1 (ZF1) before 1.12.4, Zend Framework 2 before 2.1.6 and 2.2.x before 2.2.6, ZendOpenId, ZendRest, ZendService_AudioScrobbler, ZendService_Nirvanix, ZendService_SlideShare, ZendService_Technorati, and ZendService_WindowsAzure before 2.0.2, ZendService_Amazon before 2.0.3, and ZendService_Api before 1.0.0, when PHP-FPM is used, does not properly share the libxml_disable_entity_loader setting between threads, which might allow remote attackers to conduct XML External Entity (XXE) attacks via an XML external entity declaration in conjunction with an entity reference. NOTE: this issue exists because of an incomplete fix for CVE-2012-5657.

Impact

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

Affected versions

zendframework/zendframework1 (< 1.12.4) zendframework/zendopenid (< 2.0.2) zendframework/zendrest (< 2.0.2) zendframework/zendservice-audioscrobbler (< 2.0.2) zendframework/zendservice-nirvanix (< 2.0.2) zendframework/zendservice-slideshare (< 2.0.2) zendframework/zendservice-technorati (< 2.0.2) zendframework/zendservice-windowsazure (< 2.0.2) zendframework/zendservice-amazon (< 2.0.3) zendframework/zendservice-api (< 1.0.0)

Security releases

zendframework/zendframework1 → 1.12.4 (composer) zendframework/zendopenid → 2.0.2 (composer) zendframework/zendrest → 2.0.2 (composer) zendframework/zendservice-audioscrobbler → 2.0.2 (composer) zendframework/zendservice-nirvanix → 2.0.2 (composer) zendframework/zendservice-slideshare → 2.0.2 (composer) zendframework/zendservice-technorati → 2.0.2 (composer) zendframework/zendservice-windowsazure → 2.0.2 (composer) zendframework/zendservice-amazon → 2.0.3 (composer) zendframework/zendservice-api → 1.0.0 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

zendframework/zendframework1 to 1.12.4 or later; zendframework/zendopenid to 2.0.2 or later; zendframework/zendrest to 2.0.2 or later; zendframework/zendservice-audioscrobbler to 2.0.2 or later; zendframework/zendservice-nirvanix to 2.0.2 or later; zendframework/zendservice-slideshare to 2.0.2 or later; zendframework/zendservice-technorati to 2.0.2 or later; zendframework/zendservice-windowsazure to 2.0.2 or later; zendframework/zendservice-amazon to 2.0.3 or later; zendframework/zendservice-api to 1.0.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2014-2682? CVE-2014-2682 is a medium-severity XML external entity injection (XXE) vulnerability in zendframework/zendframework1 (composer), affecting versions < 1.12.4. It is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
Which packages are affected by CVE-2014-2682?
- zendframework/zendframework1 (composer) (versions < 1.12.4)
- zendframework/zendopenid (composer) (versions < 2.0.2)
- zendframework/zendrest (composer) (versions < 2.0.2)
- zendframework/zendservice-audioscrobbler (composer) (versions < 2.0.2)
- zendframework/zendservice-nirvanix (composer) (versions < 2.0.2)
- zendframework/zendservice-slideshare (composer) (versions < 2.0.2)
- zendframework/zendservice-technorati (composer) (versions < 2.0.2)
- zendframework/zendservice-windowsazure (composer) (versions < 2.0.2)
- zendframework/zendservice-amazon (composer) (versions < 2.0.3)
- zendframework/zendservice-api (composer) (versions < 1.0.0)
Is there a fix for CVE-2014-2682? Yes. CVE-2014-2682 is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. Upgrade to this version or later.
Is CVE-2014-2682 exploitable, and should I be worried? Whether CVE-2014-2682 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-2682 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-2682?
- Upgrade zendframework/zendframework1 to 1.12.4 or later
- Upgrade zendframework/zendopenid to 2.0.2 or later
- Upgrade zendframework/zendrest to 2.0.2 or later
- Upgrade zendframework/zendservice-audioscrobbler to 2.0.2 or later
- Upgrade zendframework/zendservice-nirvanix to 2.0.2 or later
- Upgrade zendframework/zendservice-slideshare to 2.0.2 or later
- Upgrade zendframework/zendservice-technorati to 2.0.2 or later
- Upgrade zendframework/zendservice-windowsazure to 2.0.2 or later
- Upgrade zendframework/zendservice-amazon to 2.0.3 or later
- Upgrade zendframework/zendservice-api to 1.0.0 or later

Other vulnerabilities in zendframework/zendframework1

CVE-IDSeverityPackage summary

GHSA-6FQW-J3VM-7F66Criticalzendframework/zendframework1: Zendframework1 Potential SQL injection in ORDER and GROUP functions GHSA-848F-MPH5-9PM9Highzendframework/zendframework1: Zendframework Potential Information Disclosure and Insufficient Entropy vulnerability GHSA-8XHV-GQM4-3W99Highzendframework/zendframework1: ZendFramework1 Potential Insufficient Entropy Vulnerability GHSA-V42G-7Q2X-CW32Criticalzendframework/zendframework1: Zendframework1 potential SQL injection vector using null byte for PDO (MsSql, SQLite)GHSA-2X36-QHX3-7M5FCriticalzendframework/zendframework1: ZendFramework1 Potential SQL injection in the ORDER implementation of Zend_Db_Select