dbcve.org
Administration CenterApplication · Talend

CVE-2022-29943

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Talend Administration Center has a vulnerability that allows an authenticated user to use XML External Entity (XXE) processing to achieve read access as root on the remote filesystem. The issue is fixed for versions 8.0.x in TPS-5189, versions 7.3.x in TPS-5175, and versions 7.2.x in TPS-5201. Earlier versions of Talend Administration Center may also be impacted; users are encouraged to update to a supported version.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Talend Administration Center contains an XML External Entity (XXE) vulnerability that allows authenticated users to craft malicious XML payloads referencing external entities. This enables read access to files on the root filesystem of the remote server, exploiting the application's XML parser configuration.

MitigationUpdate to a supported version (7.2.x, 7.3.x, or 8.0.x) with the respective TPS patch (TPS-5201, TPS-5175, or TPS-5189). If immediate updating is not possible, disable external entity processing in the XML parser configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Administration CenterApplication
Affected:= 7.2.0= 7.3.0= 8.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Talend Administration Center version
    Locate the TAC installation directory and check the version file or use the TAC web interface help/about page to confirm the exact version number
    Affected if The installed version is exactly 7.2.0, 7.3.0, or 8.0.0
  2. Confirm user authentication is possible
    Verify that user accounts exist and authentication to Talend Administration Center is functional, either through local users or configured LDAP/SSO
    Affected if Attacker can obtain valid credentials to log into TAC
  3. Locate XML import or configuration feature
    Search for TAC features that accept XML input such as job import, configuration file upload, or data transformation settings that process user-supplied XML
    Affected if The vulnerable XML parsing endpoint accepts XML uploads or input from authenticated users
  4. Check XML parser configuration
    Examine the application server configuration files (typically in conf/ or config/ directories) for XML parser settings, specifically looking for feature flags related to external entity processing (DTD, XInclude, or external entity declarations)
    Affected if The XML parser is configured with external entity processing enabled (not disabled)
  5. Review file system access controls
    Check file system permissions on the TAC server to determine if the application server process user has read access to sensitive directories outside the application root
    Affected if The TAC process has read permissions on sensitive filesystem paths that could be targeted by XXE

User is affected if running Talend Administration Center version 7.2.0, 7.3.0, or 8.0.0 with authenticated access available and the XML parser allowing external entity processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a supported version (7.2.x, 7.3.x, or 8.0.x) with the respective TPS patch (TPS-5201, TPS-5175, or TPS-5189). If immediate updating is not possible, disable external entity processing in the XML parser configuration.

Recommended fix High confidence

Latest patched version within your current branch (7.2.x, 7.3.x, or 8.0.x) containing the respective TPS fix

  1. Obtain the appropriate Talend patch for your version: TPS-5201 for 7.2.x, TPS-5175 for 7.3.x, or TPS-5189 for 8.0.x
  2. Follow Talend's standard patch application procedure for Administration Center
  3. Apply the patch to all affected Talend Administration Center instances
  4. Restart the Administration Center services after applying the patch
  5. Verify the patch was applied successfully by confirming the XXE vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Administration Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29943 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data