LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4311: Talend Open Studio for MDM XML xml external entity reference

A vulnerability classified as problematic was found in Talend Open Studio for MDM. This vulnerability affects unknown code of the component XML Handler. The manipulation leads to xml external entity reference. The patch is identified as 31d442b9fb1d518128fd18f6e4d54e06c3d67793. It is recommended to apply a patch to fix this issue. VDB-217666 is the identifier assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Talend Open Studio for MDM has an XML handling flaw that could let an authenticated nearby attacker abuse external entity processing. Business impact is moderate: possible limited exposure, tampering, or disruption of master data workflows. The provided sources identify a patch but do not name affected versions.

Executive priority

Plan remediation in the normal vulnerability cycle, but accelerate if Talend MDM processes sensitive data or accepts XML from semi-trusted users. The lack of affected-version detail increases inventory uncertainty.

Technical view

CVE-2021-4311 is a CWE-611 XML External Entity issue in Talend Open Studio for MDM's XML Handler. CVSS 3.1 is 5.5, with adjacent access, low attack complexity, low privileges, no user interaction, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to environments running Talend Open Studio for MDM or related tmdm-server-se code paths that process XML. Affected versions are not specified in the bundle, so inventory must be source, package, or vendor-guidance based.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. VulDB classifies the issue and notes permissions are required. Treat exploit status as unconfirmed, not actively exploited from the supplied evidence.

Researcher notes

The strongest evidence is the CVE/VulDB record and GitHub patch reference. The bundle does not identify exact affected versions, vulnerable files, public exploit availability, or active exploitation. Avoid assumptions beyond CWE-611 and the referenced patch.

Mitigation direction

  • Apply the patch associated with commit 31d442b9fb1d518128fd18f6e4d54e06c3d67793.
  • Check Talend guidance for affected and fixed release mapping.
  • Limit XML-processing access to trusted authenticated users and networks.
  • Review XML parser configuration for external entity and DTD handling.
  • Monitor Talend MDM logs for unusual XML processing errors or access patterns.

Validation and detection

  • Inventory Talend Open Studio for MDM and tmdm-server-se deployments.
  • Confirm whether local code includes patch commit 31d442b9fb1d518128fd18f6e4d54e06c3d67793.
  • Map deployed builds to vendor-fixed releases when Talend guidance is available.
  • Verify XML parser hardening through code review or safe configuration checks.
  • Confirm compensating access controls around MDM XML handling paths.
Prepared
Confidence
medium
Sources
6

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.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4311 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-4311Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TalendOpen Studio for MDMn/aListed
Weakness

CWE details

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

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.