CVE-2014-2683

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 2%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
81.9%
KEV
Not listed

Published

November 16, 2014

Last Modified

May 6, 2026

References (12)

Affected Packages

(10 across 1 ecosystem)
Packagist(10)
PackageVulnerable rangeFixed inDependents
zendframework/zendframework11.12.0, 1.12.1, 1.12.2, 1.12.31.12.4—
zendframework/zendopenid2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendrest2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendservice-amazon2.0.0 ... 2.0.2 (10 versions)2.0.3—
zendframework/zendservice-api1.0.0beta11.0.0—
zendframework/zendservice-audioscrobbler2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendservice-nirvanix2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendservice-slideshare2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendservice-technorati2.0.0 ... 2.0.1 (9 versions)2.0.2—
zendframework/zendservice-windowsazure2.0.0 ... 2.0.1 (9 versions)2.0.2—

Data Freshness Timeline

(refreshed 5× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-09 19:05 UTCEPSS rescore
  2. 2026-07-08 15:10 UTCEPSS rescore
  3. 2026-07-07 13:41 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-06 02:19 UTCEPSS rescore
  6. 2026-07-05 02:26 UTCEPSS rescore
  7. 2026-07-04 06:27 UTCEPSS rescore
  8. 2026-07-02 15:21 UTCEPSS rescore
  9. 2026-07-01 15:02 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 14:03 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-22 14:22 UTCEPSS rescore
  24. 2026-06-21 14:53 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 55 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-19 19:23 UTCEPSS rescore
  3. 2026-06-18 17:49 UTCEPSS rescore
  4. 2026-06-18 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-16 17:49 UTCEPSS rescore
  10. 2026-06-15 17:44 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-12 23:08 UTCEPSS rescore
  14. 2026-06-11 13:56 UTCEPSS rescore
  15. 2026-06-10 22:15 UTCEPSS rescore
  16. 2026-06-10 13:18 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 22:44 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-04 13:09 UTCEPSS rescore
  26. 2026-06-04 13:09 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-02 20:10 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 00:14 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-29 13:41 UTCEPSS rescore
  35. 2026-05-28 15:02 UTCEG score recompute
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-27 13:38 UTCEPSS rescore
  40. 2026-05-27 13:38 UTCEPSS rescore
  41. 2026-05-26 13:41 UTCEPSS rescore
  42. 2026-05-26 13:41 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-26 07:16 UTCEPSS rescore
  45. 2026-05-24 16:43 UTCEPSS rescore
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-22 21:15 UTCEPSS rescore
  49. 2026-05-21 22:39 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-20 11:21 UTCEPSS rescore
  54. 2026-05-18 21:29 UTCEPSS rescore
  55. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2014-2683?
CVE-2014-2683 is a none vulnerability published on November 16, 2014. 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, ZendServiceAudioScrobbler, ZendServiceNirvanix, ZendServiceSlideShare, ZendServiceTechnorati, and ZendServiceWindowsAzure before 2.0.2, ZendServiceAmazon before 2.0.3, and…
When was CVE-2014-2683 disclosed?
CVE-2014-2683 was first published in the National Vulnerability Database on November 16, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-2683 actively exploited?
CVE-2014-2683 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2014-2683?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-2683, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-2683

Explore →

Is Your Infrastructure Affected by CVE-2014-2683?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs