LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25459: An issue was discovered in function sync_tree in hetero_decision_tree_guest.py in WeBank FATE (Federated AI...

An issue was discovered in function sync_tree in hetero_decision_tree_guest.py in WeBank FATE (Federated AI Technology Enabler) 0.1 through 1.4.2 allows attackers to read sensitive information during the training process of machine learning joint modeling.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-25459 is an information exposure issue in WeBank FATE, a federated learning platform. During joint machine-learning training, vulnerable versions may let an attacker read sensitive information. The public sources do not provide a CVSS score, detailed impact scope, or evidence of active exploitation.

Executive priority

Treat this as a targeted exposure review rather than a confirmed emergency. Prioritize if FATE supports sensitive joint modeling, regulated data, or partner-facing training workflows. Severity remains uncertain because public scoring and exploitation evidence are absent.

Technical view

The CVE identifies function sync_tree in hetero_decision_tree_guest.py in WeBank FATE 0.1 through 1.4.2. The flaw can expose sensitive information during the training process of machine-learning joint modeling. The source bundle references a GitHub commit but does not state a specific released fixed version.

Likely exposure

Exposure is likely limited to organizations running WeBank FATE 0.1 through 1.4.2 for federated or joint model training. Systems not using FATE, or not using affected training workflows, are not indicated as exposed by the provided sources.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. No cited source states active exploitation, exploit availability, or attacker prerequisites beyond the broad statement that attackers may read sensitive information during training.

Researcher notes

Evidence is sparse. The key facts are the affected FATE version range, vulnerable function, and information disclosure during training. The commit is relevant, but the bundle does not name a fixed release, attacker role, required access level, or exploit method.

Mitigation direction

  • Inventory WeBank FATE deployments and confirm whether versions 0.1 through 1.4.2 are present.
  • Review the referenced FATE commit and vendor guidance for the supported fix path.
  • Upgrade or patch only according to confirmed FATE project guidance.
  • Restrict access to joint training workflows until affected systems are remediated.
  • Review sensitive data used in vulnerable training runs for possible exposure.

Validation and detection

  • Confirm FATE version numbers on all training nodes and environments.
  • Check whether hetero_decision_tree_guest.py includes the referenced upstream commit changes.
  • Identify models or training jobs that used affected heterogenous decision tree workflows.
  • Review participant access and logs for unusual training-time data access.
  • Document whether vulnerable versions processed regulated or sensitive data.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2020-25459 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.