LiveActive security incident?Get immediate response
CVE Record

CVE-2020-29312: An issue found in Zend Framework v.3.1.3 and before allow a remote attacker to execute arbitrary code via t...

An issue found in Zend Framework v.3.1.3 and before allow a remote attacker to execute arbitrary code via the unserialize function. Note: This has been disputed by third parties as incomplete and incorrect. The framework does not have a version that surpasses 2.x.x and was deprecated in early 2020.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

The CVE record claims remote code execution in Zend Framework through PHP unserialize, but the record is explicitly disputed as incomplete and incorrect. It also notes Zend Framework did not have a 3.x release and was deprecated in early 2020. Treat this as an uncertain legacy-application signal, not a confirmed active emergency.

Executive priority

Do not treat this as a confirmed exploited crisis based on the provided evidence. Assign a targeted legacy-PHP review, especially for internet-facing or business-critical Zend applications, and escalate only if local unsafe deserialization is found.

Technical view

The allegation is arbitrary code execution via unsafe unserialize handling in Zend Framework <=3.1.3. The record provides no CVSS, CWE, concrete affected CPE, patch, or verified vulnerable component. The dispute note challenges the versioning and completeness of the claim, so technical validation must start from local application dependency and code evidence.

Likely exposure

Exposure is only plausible in legacy applications using Zend Framework and unserialize on untrusted or attacker-controlled data. The source bundle does not confirm affected packages, fixed versions, or deployment conditions.

Exploitation context

No source in the bundle states active exploitation, and the CVE is not marked KEV. Public evidence is thin and disputed, so exploitation likelihood cannot be assessed confidently from these sources.

Researcher notes

The record is internally inconsistent because it names Zend Framework v3.1.3 while noting the framework did not surpass 2.x. There is no CVSS, CWE, CPE, patch reference, or reproducible technical detail in the bundle.

Mitigation direction

  • Inventory applications for Zend Framework or abandoned Zend packages.
  • Review vendor and project guidance before assigning emergency patch work.
  • Avoid unserialize on untrusted data in legacy PHP code paths.
  • Prioritize migration from deprecated Zend Framework where business-critical.

Validation and detection

  • Check dependency manifests for zendframework packages and versions.
  • Confirm whether any code calls unserialize on external input.
  • Document whether the application still depends on deprecated Zend Framework components.
  • Track the CVE record for clarification, rejection, or corrected affected versions.
Prepared
Confidence
low
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-29312 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.