dbcve.org
Administration CenterApplication · Talend

CVE-2022-31648

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

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 is vulnerable to a reflected Cross-Site Scripting (XSS) issue in the SSO login endpoint. The issue is fixed for versions 8.0.x in TPS-5233, for versions 7.3.x in TPS-5324, and for versions 7.2.x in TPS-5235. 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 a reflected Cross-Site Scripting (XSS) vulnerability in the SSO login endpoint. Attackers can inject malicious scripts through the endpoint that execute in victim browsers when they access the crafted URL. This is a reflected XSS where user-supplied input is returned to the user without proper sanitization.

MitigationUpdate Talend Administration Center to version 7.2.x, 7.3.x, or 8.0.x to obtain the respective patches TPS-5235, TPS-5324, or TPS-5233. Earlier vulnerable versions should be upgraded to a supported release.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 version file in the TAC installation directory or access the Administration Center web interface and navigate to the About or System Information page to retrieve the installed version number
    Affected if The installed version is exactly 7.2.0, 7.3.0, or 8.0.0
  2. Confirm SSO login endpoint is accessible
    Check if the SSO login endpoint is exposed on the Talend Administration Center web server. This is typically found at a URL path related to SSO authentication or SAML login. Verify the endpoint responds to HTTP requests.
    Affected if The SSO login endpoint is publicly or internally accessible over the network
  3. Determine if SSO authentication is enabled
    Review the Talend Administration Center configuration files (such as TalendAdManCenter/configuration/talend-config.properties or similar configuration files) to check whether SSO or SAML authentication has been enabled
    Affected if SSO or SAML authentication is configured and enabled in the Talend Administration Center configuration
  4. Verify web interface is exposed
    Confirm the Talend Administration Center web interface is reachable via browser on the configured HTTP/HTTPS port (default is 8080 for Tomcat installations). Test access to the login page.
    Affected if The web interface is accessible and the application is running

You are affected if Talend Administration Center is installed at exactly version 7.2.0, 7.3.0, or 8.0.0 and the SSO login endpoint is accessible and enabled in your environment

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 Talend Administration Center to version 7.2.x, 7.3.x, or 8.0.x to obtain the respective patches TPS-5235, TPS-5324, or TPS-5233. Earlier vulnerable versions should be upgraded to a supported release.

Recommended fix Moderate confidence

Latest patch version in current branch (7.2.x/7.3.x/8.0.x) containing respective TPS fix

  1. Identify current Talend Administration Center version in use
  2. Determine which version branch (7.2.x, 7.3.x, or 8.0.x) is currently deployed
  3. Upgrade to the latest available patch version within the same major.minor branch that includes the TPS fix:
  4. - For 8.0.x branch: upgrade to latest 8.0.x version containing TPS-5233
  5. - For 7.3.x branch: upgrade to latest 7.3.x version containing TPS-5324
  6. - For 7.2.x branch: upgrade to latest 7.2.x version containing TPS-5235
  7. If on an earlier unsupported version (below 7.2.0), plan migration to a supported version (7.2.x, 7.3.x, or 8.0.x)
  8. After upgrade, verify the SSO login endpoint is no longer vulnerable to reflected XSS
Caveat Review Talend compatibility matrix and release notes for any breaking changes between versions; test upgrade in staging environment before production deployment

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-31648 — 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-31648 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