How severe is CVE-2014-2683?

No CVSS score has been assigned to CVE-2014-2683 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2014-2683?

Affected package information for CVE-2014-2683 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2014-2683?

Apply the zend zend framework security patch or hotfix for CVE-2014-2683 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2014-2683 across my infrastructure?

Inventory every zend zend framework deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2014-2683 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2014-2683?

O3 detects and blocks CVE-2014-2683 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2014-2683 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-2683 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-2683?

CVE-2014-2683 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-2683?

CVE-2014-2683 is classified as CWE-17 (CWE-17). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2014-2683?

CVE-2014-2683 affects zend zend framework; zend zendopenid; zend zendrest; zend zendservice amazon, and 6 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2014-2683 published, and has it been updated?

CVE-2014-2683 was published on November 16, 2014 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2014-2683: Zend Framework CWE-17

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk82th percentile-0.19%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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 cause a denial of service (CPU consumption) via (1) recursive or (2) circular references in an XML entity definition in an XML DOCTYPE declaration, aka an XML Entity Expansion (XEE) attack. NOTE: this issue exists because of an incomplete fix for CVE-2012-6532.

Affected Products

10 products · 12 configurations

Application

zend frameworkzend

≥ 2.2.0 && < 2.2.6

range

Application

zendopenidzend

≤ 2.0.1

range

Application

zendrestzend

≤ 2.0.1

range

Application

zendservice amazonzend

≤ 2.0.2

range

Application

zendservice apizend

≤ 1.0.0

range

Application

zendservice audioscrobblerzend

≤ 2.0.1

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every zend zend framework deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the zend zend framework security patch or hotfix for CVE-2014-2683 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2014-2683 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2014-2683. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 cause a denial of service (CPU consumption) via (1) recursive or (2) circular references in an XML entity definition in an XML DOCTYPE declaration, aka an XML Entity Expansion (XEE) attack. NOTE: this issue exists because of an incomplete fix for CVE-2

O3 Security · Runtime Protection

Is CVE-2014-2683 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2014-2683 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2014-2683

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2014-2683 being exploited in your environment?