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 packages are affected by CVE-2014-2683?

CVE-2014-2683 affects the following packages: zendframework/zendframework1 (Packagist), zendframework/zendopenid (Packagist), zendframework/zendrest (Packagist), zendframework/zendservice-audioscrobbler (Packagist), zendframework/zendservice-nirvanix (Packagist), zendframework/zendservice-slideshare (Packagist), zendframework/zendservice-technorati (Packagist), zendframework/zendservice-windowsazure (Packagist), and 2 more. Ecosystems affected: Packagist.

How do I fix CVE-2014-2683?

Update zendframework/zendframework1 to 1.12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2683 is resolved across your whole dependency graph.

How do I detect CVE-2014-2683 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 84th 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.

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

CVE-2014-2683 was published on May 14, 2022 and was last updated on December 7, 2024. 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: zendframework1 DoS

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

10 pkgs affected

🐘zendframework/zendframework1🐘zendframework/zendopenid🐘zendframework/zendrest🐘zendframework/zendservice-audioscrobbler🐘zendframework/zendservice-nirvanix🐘zendframework/zendservice-slideshare🐘zendframework/zendservice-technorati🐘zendframework/zendservice-windowsazure+2 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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 Packages

10 total 10 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zendframework/zendframework1`	all versions	1.12.4`composer require zendframework/zendframework1:^1.12.4`
🐘Packagist	`zendframework/zendopenid`	all versions	2.0.2`composer require zendframework/zendopenid:^2.0.2`
🐘Packagist	`zendframework/zendrest`	all versions	2.0.2`composer require zendframework/zendrest:^2.0.2`
🐘Packagist	`zendframework/zendservice-audioscrobbler`	all versions	2.0.2`composer require zendframework/zendservice-audioscrobbler:^2.0.2`
🐘Packagist	`zendframework/zendservice-nirvanix`	all versions	2.0.2`composer require zendframework/zendservice-nirvanix:^2.0.2`
🐘Packagist	`zendframework/zendservice-slideshare`	all versions	2.0.2`composer require zendframework/zendservice-slideshare:^2.0.2`

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

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zendframework/zendframework1 to 1.12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2683 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 · Impact-Aware SCA

Is CVE-2014-2683 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-2683 — zendframework1

EPSS Exploitation Probability

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2014-2683 in your dependencies?