dbcve.org
Data CatalogApplication · Talend

CVE-2021-42837

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-05
Fix available
A fix is available. Upgrade to 7.3-20210930 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in Talend Data Catalog before 7.3-20210930. After setting up SAML/OAuth, authentication is not correctly enforced on the native login page. Any valid user from the SAML/OAuth provider can be used as the username with an arbitrary password, and login will succeed.

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

In Talend Data Catalog versions prior to 7.3-20210930, when SAML/OAuth authentication is configured, the native login page fails to properly enforce credential validation. The system accepts any valid user identity from the configured SAML/OAuth identity provider combined with an arbitrary/invalid password, successfully granting access without proper authentication.

MitigationUpgrade to Talend Data Catalog version 7.3-20210930 or later. Alternatively, disable or restrict access to the native login page if SAML/OAuth authentication is the sole authentication method, and audit access logs for any unauthorized access attempts.

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:< 7.3-20210930

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

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

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. Determine Talend Data Catalog installed version
    Access the application administration console or About page to identify the exact version number running in your environment. Common locations include the Help > About menu in the application or the system information endpoint.
    Affected if The installed version is lower than 7.3-20210930 (e.g., 7.2.x, 7.1.x, or earlier releases).
  2. Verify SAML authentication is configured
    Navigate to the authentication or security settings within the Talend Data Catalog administration interface. Look for SAML identity provider (IdP) configuration sections and confirm SAML is enabled.
    Affected if SAML authentication is enabled and configured as an authentication method.
  3. Verify OAuth authentication is configured
    Navigate to the authentication or security settings within the Talend Data Catalog administration interface. Look for OAuth/OpenID Connect provider configuration sections and confirm OAuth is enabled.
    Affected if OAuth authentication is enabled and configured as an authentication method.
  4. Confirm native login page is accessible
    Access the standard Talend Data Catalog login page directly (typically the base URL without SAML/OAuth redirect). Verify the native username/password form is available for authentication attempts.
    Affected if The native login page is accessible and accepts user credentials without redirecting to the SAML/OAuth provider.

You are affected if your Talend Data Catalog version is below 7.3-20210930 AND either SAML or OAuth authentication is configured, because the native login page will accept a valid SAML/OAuth user identity with any password to grant access.

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 7.3-20210930 or later
Fixed in 7.3-20210930
Interim mitigation

Upgrade to Talend Data Catalog version 7.3-20210930 or later. Alternatively, disable or restrict access to the native login page if SAML/OAuth authentication is the sole authentication method, and audit access logs for any unauthorized access attempts.

Recommended fix High confidence

7.3-20210930 or later

  1. 1. Back up your current Talend Data Catalog configuration and database
  2. 2. Review the Talend 7.3 release notes for any migration requirements or breaking changes
  3. 3. Download Talend Data Catalog version 7.3-20210930 or later from the Talend support portal
  4. 4. Stop the Talend Data Catalog application services
  5. 5. Install the new version following the standard Talend upgrade documentation
  6. 6. Restore your configuration from the backup
  7. 7. Start the application services
  8. 8. Verify that SAML/OAuth authentication is working correctly
Caveat Review release notes for version 7.3 for any migration requirements or changes that may affect your configuration

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

Fix this in Data Catalog Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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