CVE-2014-2681

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 allow remote attackers to read arbitrary files, send HTTP requests to intranet servers, and possibly cause a denial of service (CPU and memory consumption) via an XML External Entity (XXE) attack. NOTE: this issue exists because of an incomplete fix for CVE-2012-5657.

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.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2014-2681? CVE-2014-2681 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.
2. Which packages are affected by CVE-2014-2681?
   • 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)
3. Is there a fix for CVE-2014-2681? Yes. CVE-2014-2681 is fixed in 1.12.4, 2.0.2, 2.0.3, 1.0.0. Upgrade to this version or later.
4. Is CVE-2014-2681 exploitable, and should I be worried? Whether CVE-2014-2681 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
5. What actually determines whether CVE-2014-2681 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.
6. How do I fix CVE-2014-2681?
   • 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