dbcve.org
Data CatalogApplication · Talend

CVE-2023-36301

HIGH · 7.5 CVSS v3.1 Published 2023-06-26
Fix available
A fix is available. Upgrade to 8.0-20230221 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 before 8.0-20230221 contain a directory traversal vulnerability in HeaderImageServlet.

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 Data Catalog versions prior to 8.0-20230221 contain a directory traversal vulnerability in the HeaderImageServlet component. This allows attackers to access files outside the intended directory by manipulating file paths with '..' sequences, potentially exposing sensitive system files.

MitigationUpgrade Talend Data Catalog to version 8.0-20230221 or later. Alternatively, implement input validation and path sanitization in the HeaderImageServlet to reject paths containing directory traversal sequences.

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-20230221

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Data Catalog installation
    Locate the Talend Data Catalog installation directory or check for the 'HeaderImageServlet' component in your web application server (commonly Tomcat or similar). Look for war files or deployed applications containing 'talend' or 'datacatalog' in the path.
    Affected if Talend Data Catalog is installed and the application server is running.
  2. Determine installed version
    Check the application version through the Talend admin console, version.info file in the installation directory, or the application startup logs. Compare the version to 8.0-20230221.
    Affected if The installed version is earlier than 8.0-20230221 (e.g., 7.x, 8.0-20220815, etc.).
  3. Verify HeaderImageServlet is exposed
    Identify if the HeaderImageServlet is accessible via the web interface. This servlet typically handles image loading and is located at a path containing 'HeaderImage' or similar in the URL pattern. Check your web.xml or exposed endpoints.
    Affected if The HeaderImageServlet is accessible and handles file path parameters without validation.
  4. Test for directory traversal vulnerability
    Send a request to the HeaderImageServlet endpoint with a path containing '..' sequences (e.g., /HeaderImage?file=../../config.xml or similar path pattern). Observe if the application returns files from outside the intended directory.
    Affected if The servlet returns files from arbitrary directories when '..' sequences are used in the request path.

A system is affected if Talend Data Catalog is running with a version earlier than 8.0-20230221 and the HeaderImageServlet is accessible, allowing directory traversal via '..' sequences in file path parameters.

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-20230221 or later
Fixed in 8.0-20230221
Interim mitigation

Upgrade Talend Data Catalog to version 8.0-20230221 or later. Alternatively, implement input validation and path sanitization in the HeaderImageServlet to reject paths containing directory traversal sequences.

Recommended fix High confidence

8.0-20230221 or later

  1. 1. Back up your current Talend Data Catalog installation and database
  2. 2. Download Talend Data Catalog version 8.0-20230221 or later from the official Talend downloads portal
  3. 3. Follow Talend's official upgrade documentation for your deployment type (help.talend.com)
  4. 4. Restart the Data Catalog services after upgrade
  5. 5. Verify the HeaderImageServlet is accessible and path traversal vulnerability is resolved by testing with valid image paths

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

Fix this in Data Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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