dbcve.org
Data CatalogApplication · Talend

CVE-2023-33247

HIGH · 7.5 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to 8.0-20230413 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Data Catalog remote harvesting server before 8.0-20230413 contains a /upgrade endpoint that allows an unauthenticated WAR file to be deployed on the server. (A mitigation is that the remote harvesting server should be behind a firewall that only allows access to the Talend Data Catalog server.)

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

The Talend Data Catalog remote harvesting server versions before 8.0-20230413 contains an unprotected /upgrade endpoint that accepts WAR file uploads without authentication, allowing remote attackers to deploy arbitrary web applications and potentially achieve remote code execution.

MitigationDeploy the remote harvesting server behind a firewall that restricts network access to only the legitimate Talend Data Catalog server, preventing unauthorized external access to the /upgrade endpoint.

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
Data CatalogApplication
Affected:< 8.0-20230413

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Data Catalog installation
    Locate the Talend Data Catalog installation directory or check for running services related to Talend. Common paths include /opt/talend or C:\Talend. On Linux, run 'ps -ef | grep talend' to find running processes.
    Affected if Talend Data Catalog remote harvesting server is installed and running.
  2. Determine the installed version
    Check the version of the Talend Data Catalog installation. Look for a version file in the installation directory, or check the application banner/about page. Compare the version to 8.0-20230413.
    Affected if The installed version is earlier than 8.0-20230413.
  3. Verify remote harvesting server is deployed
    Identify if the remote harvesting server component is deployed. This is typically a separate WAR file or service. Check the application server (Tomcat, etc.) deployment directory for remote harvesting related WAR files.
    Affected if The remote harvesting server WAR file is deployed on the application server.
  4. Check network accessibility of /upgrade endpoint
    Test network access to the /upgrade endpoint on the remote harvesting server. Use a tool like curl: 'curl -I http://<server>:8080/<context>/upgrade'. Check if the endpoint responds without requiring credentials.
    Affected if The /upgrade endpoint is accessible over the network without authentication.
  5. Confirm endpoint accepts unauthenticated uploads
    Attempt a POST request to the /upgrade endpoint without authentication headers. Send a minimal test request (such as an empty or dummy WAR file) and observe the server response.
    Affected if The server accepts file uploads at /upgrade without requiring authentication.

The environment is affected if Talend Data Catalog remote harvesting server version is earlier than 8.0-20230413 and the /upgrade endpoint is network-accessible without authentication.

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
Upgrade available Upgrade to 8.0-20230413 or later
Fixed in 8.0-20230413
Interim mitigation

Deploy the remote harvesting server behind a firewall that restricts network access to only the legitimate Talend Data Catalog server, preventing unauthorized external access to the /upgrade endpoint.

Recommended fix High confidence

8.0-20230413 or later

  1. Upgrade Talend Data Catalog to version 8.0-20230413 or later to remediate the missing authentication vulnerability
  2. After upgrading, verify the /upgrade endpoint is no longer accessible without authentication
  3. As an additional defense-in-depth measure, ensure the remote harvesting server is placed behind a firewall that only allows access from the Talend Data Catalog server

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

Fix this in Data Catalog Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33247 — 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-2023-33247 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