dbcve.org
Testcomplete SupportApplication · Jenkins

CVE-2023-33002

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to after 2.8.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins TestComplete support Plugin 2.8.1 and earlier does not escape the TestComplete project name, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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 Jenkins TestComplete support Plugin versions 2.8.1 and earlier fails to properly escape the TestComplete project name when rendering it in the UI, allowing stored XSS. Attackers with Item/Configure permission can inject malicious JavaScript via the project name field which executes when other users view the affected page.

MitigationUpgrade the TestComplete support Plugin to version 2.8.2 or later, which includes proper output encoding for the project name field.

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
Testcomplete SupportApplication
Affected:<= 2.8.1

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

CVSS:3.1/AV:N/AC:L/PR:L/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 installed TestComplete Support Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use Jenkins CLI: jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i testcomplete. Alternatively check the manifest file in the plugin war/folder.
    Affected if Plugin version is 2.8.1 or earlier, or version cannot be determined (plugin may not be installed)
  2. Verify plugin is actively used in jobs
    Search job configurations for TestComplete-related steps. Use Jenkins script console: Jenkins.instance.allItems.collect { it.class }.contains(hudson.tasks.TestComplete) or search config.xml files for '<testComplete' entries in $JENKINS_HOME/jobs/
    Affected if Any job contains TestComplete build steps with project names configured
  3. Check for TestComplete project name field in job configurations
    Review job configuration pages (Job > Configure) or inspect config.xml files for the <projectName> or <ProjectName> field within TestComplete-related elements.
    Affected if Jobs contain TestComplete project name values (regardless of content, the rendering is vulnerable)
  4. Assess user access to affected views
    Determine which users have Item/Read or Item/ViewPermission access to jobs with TestComplete configurations. Check Matrix-based security or project-based authorization settings.
    Affected if Users other than the job configurer can access and view job pages where TestComplete project names are displayed

User is affected if the TestComplete Support Plugin version is 2.8.1 or earlier AND there are jobs with TestComplete project name configurations that other users can view.

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 a release after 2.8.1
Interim mitigation

Upgrade the TestComplete support Plugin to version 2.8.2 or later, which includes proper output encoding for the project name field.

Recommended fix High confidence

2.8.2 or later

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Installed' tab
  4. 4. Locate the 'TestComplete Support' plugin in the list
  5. 5. If an update is available, click 'Update now' to upgrade to version 2.8.2 or later
  6. 6. Restart Jenkins if required to complete the installation

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

Fix this in Testcomplete Support Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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